We talked about the Parent Token Context of an Executable Campaign recently. Remember? It was this little switch:
Today, I was tasked to create a chain of Smart Campaigns where the executed campaign should write a value into a field based on a trigger token.
First of all, we have to understand this:
The trigger reacts to any form submit. The Flow Step writes the URL of the form page into the field “Last Form URL”. If you’re unfamiliar with trigger tokens, read more here. (It’s a little unfortunate that Adobe named this page “Trigger Tokens for Interesting Moments”, as trigger tokens are by no means limited to Interesting Moments.)
Okay, in this case above we want to write the page URL of the last form submit into a field. That works beautifully.
But what if we wanted/needed to do it differently? The trigger campaign is supposed to send a Sales Alert email, and that Sales Alert email is supposed to list that Last Form URL – to give Sales context – but the campaign that writes this value is centralized and somewhere else. Can we execute it?
When we create an Executable Smart Campaign with this flow step, it looks like this:
Well, sure. D’oh! We don’t have a trigger, as this campaign is executed. But: Can we do this?
Will the switch on “Use Parent Campaign Token Context” hand down the trigger token to the executed campaign?
And the answer, my friends, is yes. Once you execute the campaign the red squiggly lines vanish and the Smart Campaign works.
