Darshil_Shah1

Congratulations all!Looking forward to collaborating, learning, and sharing with all! Let's go.

Thank you so much, @Michael_Florin! I feel lucky and honored being part of such an awesome community of users!Hope you have a good week. 🙂

Similar thread here!Fyi: In order for Marketo to map values back into a field, the webhook response code must be of the form 2xx . If the intent of the webhook is to change values in the Marketo lead record via the response, then the Web Service which is called must return 2xx, all other response co...

Are you able to see the first name getting updated for the lead record in dynamics as per the updates made in Marketo?

Ahh, just rechecked in the actual email - we also had the image CTA URL tokenized to which we added the protocol in front (and thought that was being referred)! Actual Image address URL was used as is (as per the snapshot), i.e., w/o protocol in front and it worked flawlessly for us! Lotta confusion...

Thank you, @Katja_Keesom!Agreed, protocol shouldn't be added to the tokenized URLs! Snapshots in the post are for ref only from a test email! We added the protocol in front of the token while selecting the image. 🙂

Thanks for confirming, @david-zweben ! Can you please share the snapshot of the person’s activity log where you see the stale data getting appended by the campaign flow step after the value on Person Status field has updated (which actually triggered off the update campaign)?

Ahaa, this works too. Thank you, Ellen!

I've never faced this kind of issue even in pretty loaded/slow instance with the stale value getting appended to the field - since the campaign itself triggers when the data value change happens on the person's field in the lead database, and Marketo's flow step is gonna reference the same person fi...