I’m gonna teach you — live — how to correctly integrate reCAPTCHA v3 into Marketo forms
We’re doing it live! (Because I’ve always thought there were too many precise steps for a blog post.) →
Let Todd @ Sponge tell you how FlowBoost can merge Munchkin activities with non-Marketo forms
Todd Sprinkel’s a friend and tech whiz (I subscribe to his newsletter, if that tells you anything!) and he just came out with a FlowBoost-related post I can’t →
Inverting the submitted value of a Forms 2.0 Checkbox
A checked Checkbox doesn’t always mean String “yes”/Boolean true. Depending on your form logic and db schema, checked may correspond to “no”/false in the database, while unchecked is “yes”/true. The Forms 2.0 library assumes checked means “yes” but with some crafty code we can flip it. →
Extending jQuery’s “is” with “before is” and “after is” event listeners
Sometimes, even I have to admit that Marketo Forms being jQuery-based — as opposed to using vanilla JS — makes custom/hacky behaviors easier to implement. →
You must be joking
The worst attempt at form anti-spam prevention I’ve seen yet. →
Disturbingly detailed Velocity: $string.substring(0,$string.length()) isn’t doing what you think
Memory matters: if your Velocity code is inefficient and/or too obscure to be optimized, you can slow or even crash your Marketo instance. →
Creating trackable links even when a token includes “http://” or “https://”
If your stored URLs (in both URL and String fields) include the protocol — as you‘d assume they should! — that makes them non-trackable. Velocity can make ‘em trackable again. →
Don’t choose “promo” as your Marketo LP subdomain (that is, promo.example.com)
You might think choosing an LP subdomain (pages.example.com, get.example.com, etc.) is just a branding thing. But there are a few hostnames you must not choose, for quirky technical reasons. →