Hi Sanford,
This is in continuation to our discussion on "Accessing tag values" thread. Opening a new thread as "Accessing tag values" was marked as solved.
Quick recap from the previous thread
Now, I am thinking of following approach
Is "Not Webhook is Called" as a choice in flow step guarantees that Webhook is called only once ? Can you please help me to understand more on "Not Webhook is Called".
Please suggest.
Thanks,
Babu
Solved! Go to Solution.
You only need the webhook to execute once for the campaign. It doesn't matter whether the first person to run through the campaign runs the webhook or the last, or someone in the middle.
Not Webhook is Called only pertains to the current record going through the flow. It’s not a global filter. (Note almost no Marketo Engage filters are cross-record; the only exception is the Possible Duplicates filter because it compares the current record to other records.)
You would have to use a resource record — that is, a person record dedicated to this purpose — to call the webhook. Add that record to the send campaign.
Thank you, Sanford!
So I would have to
If my understanding is correct
Hope I understand your idea correctly.
Thanks,
Babu
Why are you worried about the order?
Say for example, if abc@test.com gets processed before email@test.com then webhook will not be called because of email address comparison to email@test.com. In such case UTM parameters will not be populated with tag values in the email that was sent to abc@test.com.
Thanks,
Babu
Got it. Thank you Sanford!
Thanks for your help!
Thanks,
Babu
I have one more question, Sanford.
In case of failing to execute Webhook
Thanks,
Babu
You can trigger on Webhook is Called and constrain on the Response. That lets you see all kinds of HTTP-level errors and even unexpected content in the response.
Thank you so much, Sanford!
Thanks,
Babu