Be smart about “dummy” email addresses
Sometimes you need a valid-looking email address as a placeholder, but you must be sure that it truly doesn't exist — so you don't send, or even →
Bug-like behavior in Forms 2.0 w/multiple Munchkin cookies
This one's more of a technical curiosity than a pressing concern for most people. But if it's biting you, it's definitely noteworthy. As you →
Those bulletproof buttons are also *tracking*-proof, though…
Some time back, the folks at Campaign Monitor contributed the go-to fancy button builder for cross-device emails, Bulletproof email buttons [https://buttons.cm/] . If you haven't seen it, →
“Tested in Chrome” is still not enough (*sigh*)
If you've wondered why devs still ask you for “the OS, browser vendor, and browser version” after all these years, when browser features seem so converged: it' →
Protecting your Thank You/Download pages from direct visits… by newbies
This one comes up periodically in the Community, so thought I'd set out the answers for next time. Thank You (a.k.a. Follow Up/Download) pages shown →
An obscure Marketo Forms 2.0 bug with Known Lead HTML + non-English characters
If your Marketo forms are only in English — or even if you work in other languages, but the buttons on your forms only use unaccented ASCII characters — you'd →
Generating Munchkin Associator Tokens in SFDC/Apex or FlowBoost/JS
💡Unfortunately, Marketo no longer supports the Munchkin associateLead function so this post is obsolete as of 2021-ish. Kept around for posterity. The code in this post is used in the →
Redirector pages: why #hash instead of ?query
This was originally a P.S. in the redirector page [https://blog.teknkl.com/stop-using-direct-download-links-unless-you-like-losing-tracking/] post, but I figured it deserved a post of its own. In other redirector page →