Marketo’s onValidate and friends stack like DOM event listeners: they run in the order they were added. But there are still major differences: 1. In Marketo, the listener stack →
The tl;dr: gotta use the API to use the API. When browsing Marketing Activities, you’ll see the URL change to reflect Program IDs, Static List IDs, and Smart →
Getting web analytics 100% in sync between Munchkin and GA4/Clicky/etc. is still a pipe dream, but here’s one reason they differ. →
Way too many URL builders are naïve about how tokens work. (Not just Marketo tokens, but other platforms’ variables/tokens/merge fields as well.) →
No pressing need to do this, but it can help you & your site feel more up-to-date. →
Together, the {{trigger.Web Page}} and {{trigger.Query Parameters}} tokens can recreate a visited URL. But parsing the URL into separate fields can’t be done natively: you need FlowBoost. →
You’re just one unencoded (or wrongly-encoded) query param away from a broken form. Scary, right? →
I might be unhealthily obsessed with form events. But not testing against worst cases is how you get “randomly” broken forms. →