Inserting ﹤style﹥ elements into mktoText areas (without having ’em stripped out)

Marketo gets curiously angry when you try to add <style> elements in the Rich Text Editor, though such elements can make strategic sense. They don’t apply the same punishment to <script> elements nor custom elements, so that gives us a workaround. →

Stop email clients from hyperlinking text that’s merely “URL-like”

Call it an unwelcome feature, call it a bug, call it a security vulnerability. Whatever you call it, here’s how to call it off (mostly). →

Velocitip: Reformat phone numbers for local display and “deformat” numbers for tel: links

Phone numbers can take many formats (Marketo, like most apps, treats them as strings under the hood). If you want to use a standard format in outbound emails, Velocity can help. →

Simulate Visibility Rules to show/disable/hide the Submit button on Marketo forms

Native Visibility Rules can’t manage the Submit button state, but a little custom JS can. →

What’s the difference between a single-form loadForm() callback and the all-forms whenReady()?

This one’s pretty esoteric, but it’s good to know if you’re applying to be a Master of Forms™. →

Managing form dropdown options at the LP level

Rather than creating a whole new form for an audience that’s only slightly different, you can manage dropdown options per-LP. →

In Form Editor, “null” isn’t the same as NULL (huh?)

Null values (as opposed to empty values) can be hard to grasp in general, and Marketo doesn’t help by using multiple meanings. →

Enabling reCAPTCHA v2 for multiple Marketo forms on the same page

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 →