Forcing a Marketo form to create a new person on every fillout
This one takes so little code, I took the liberty of tagging it as “no JS.“ There are a few lines to place on your LP, but the rest is drag-and-drop-and-type in the Marketo UI. →
If you absolutely *must* load embeds from different domains
Whenever you can, standardize your form embeds on a single Marketo LP domain. But there’s one case where you clearly can’t: different Marketo instances. →
Combining Progressive Profiling with (the equivalent of) Known Visitor HTML
Progressive Profiling and native KV HTML don’t play well together, but if you build a KV HTML equivalent using a little CS + JSS, you get the best of both worlds. →
Patching a bug with input masks + multiple Marketo forms on the same page
Unbeknownst to (I’m pretty sure) anyone, whether input masks work or not depends on form load order. →
The dreaded “Submission failed, please try again” error and how you caused it 😊
Panic-inducing for sure, but every time I’ve seen this error there’s a straightforward cause and easily deployed solution. You just need to know where to look. →
Transforming Marketo-incompatible webhook responses using AWS API Gateway + JSONPath + Velocity (!)
Velocity ain’t just a Marketo thing! Having a command of VTL loops and conditions lets you use a totally different environment — Amazon Web Services — to better integrate prepackaged webhooks. →
No, you do not need to add a “Wait” after “Change Data Value” to use the new value
Unfortunately, this advice is still heard in the wild. Let’s try to take it out of circulation. →
Sure, spaces in an ˂a href˃ or ˂img src˃ make it invalid — but “invalid” doesn’t mean what you think it means!
Retracing how a web standard got rumor-milled into incorrect, anxiety-producing conventional wisdom. →