Parse “Visit Web Page” {{trigger.tokens}} into individual query params using FlowBoost

Marketo uses offbeat definitions when it comes to web visits. For example, if you visit this URL in your browser: https://example.com/page/4?utm_campaign=2026-01-sample-sale&utm_

Properly preserving Marketo {{dotted.tokens}} in URL builders

Busy MOps teams use a URL builder to manage tracking params (and sometimes for add-to-calendar URLs and other areas). They have a UI like this: And generate a copy-and-pasteable URL

Streamline the Munchkin embed code, taking out outdated cruft

In my last post on the bfcache I mentioned the Munchkin library does some backward-compatible stuff that’s not necessary in modern browsers (it was only relevant for old versions

Why the back/forward cache (bfcache) loses Munchkin activities, and how to fix it

Modern browsers use the back/forward cache (“bfcache”) to accelerate simple ⇦ and ⇨ navigation. Confusingly, the bfcache is different from both the classic HTTP cache and the new Cache API, and

Be aware of decodeURIComponent() limitations (not only with Marketo forms, but with any 1ˢᵗ or 3ʳᵈ party JS)

You’re just one unencoded (or wrongly-encoded) query param away from a broken form. Scary, right?

MktoForms2.whenReady() is always non-blocking (plus: what is and isn’t a race condition)

I might be unhealthily obsessed with form events. But not testing against worst cases is how you get “randomly” broken forms.

Tip: Add a initial row number to Bulk Lead Import CSVs for useful failure reports

Ideally, you should pre-flight CSVs (i.e. check for core errors) before sending ’em to the Bulk API. If you can’t do that, at least add a column to all CSVs to make post-processing easier.

No, you don’t need a Wait step after Sync Person to SFDC: sync-related updates are immediate (i.e. synchronous)

Don’t let paranoia get the better of you: the Marketo-SFDC connector is very smart about order of operations.