If you see an “EventEmitter memory leak” error in your browser console, you've almost certainly done something wrong in JS. But don't take it personally: that something might've been innocently copying-and-pasting code from the Marketo developer docs →
When you select "If Known Visitor, show Custom HTML" for a Forms 2.0 form, you get a built-in "Not You?" link. But what if you want to offer that same functionality while still showing the original form? →
Velocity's MathTool.random() function can randomize content across leads, an easy form of A/B testing. →
Even if you're skilled at JavaScript in general, you still need to understand Marketo Forms JS in particular. Otherwise, your best-intentioned form behaviors won't quite work. →
JavaScript is so flexible, and so quickly evolving, that you can meet a tiny tech requirement in infinite ways. Even after kicking out broken code and bad-code-that-sort-of-works, you have lots of equally right ways left to choose from. Let's build one of those right ways. →
I've written before about disabling Munchkin for certain IP ranges, and about custom Munchkin options on Marketo LPs (where Munchkin is injected automatically with special options). Honoring anti-cookie/anti-tracking legislation like GDPR requires a combo of these earlier concepts. →
You probably don't realize that Munchkin ignores clicks, by default and by (curious) design, on 6 different types of links. Let's dive in! →
The epithet “designed by developers” may not be one you've heard. (And that's okay: most people who read this blog have kept up their automatic respect for techies longer than I have.) →