SanfordWhiteman

Visibility Rules work for any field on a Marketo form, but they don't work for the submit button itself. So if you want to hide – or at least visually disable/gray out – the button based on certain field values, a little Forms 2.0 JS is needed. In brief, the code below listens for a standard (that i...

Let’s say you want to immediately switch to lightbox mode (using the Forms 2.0 native lightbox() feature) when a specific form is ready. You’d think there’d be zero difference between Approach #1: MktoForms2.whenReady(function(mktoForm){ if(mktoForm.getId() == 1234) MktoForms2.lightbox(mktoFo...

This post is an experiment: can a cool technical hack be communicated without extra prose... that is, can I shut up for once? If it doesn’t make sense, ask in the comments! 😉 In Form Editor, just add the field with type Select — options don’t need to be listed there. ...

You don’t really know Marketo forms until you grok the differences between these 3 form field setups: Setup #1 This first screenshot is what you get simply by adding a field and flipping its type to Hidden.The field is set to have an empty string as the default value, as you can see in the field det...

Many of you use my Forms 2.0 JS snippets to integrate reCAPTCHA v2 or v3 with Marketo. (While Marketo will have native support for reCAPTCHA in the future, as of now you need to set it up yourself.) To my shame, the existing reCAPTCHA v2 code doesn’t work with multiple forms on the same page, since ...

A classic data disaster. If you don’t make a study of encoding, it’ll make a study of you! It was all fun and games until this: Turned into this: Here’s the old value translated into English, if you’re curious: The new value, of course, is gibberish. A specific type of gibberish, to be sure — UTF-8...