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 →
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_ →
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 →
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 →
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 →
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. →
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. →
Don’t let paranoia get the better of you: the Marketo-SFDC connector is very smart about order of operations. →