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. →
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. →
The worst attempt at form anti-spam prevention I’ve seen yet. →
Memory matters: if your Velocity code is inefficient and/or too obscure to be optimized, you can slow or even crash your Marketo instance. →
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. →
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. →
If a SaaS app lets you store certain characters in a field, your offline data warehouse (or data lake, or archive, or whatever) must support those same characters, no matter how rarely used. →
Use this little bit of JS to pass submitted form values across sites, from a Marketo form on Domain A to a Thank You page on Domain B. →