2 flavors of autofill for multivalued fields: Original (semicolons) and Extra Spicy (standards-based)

Easy to fill a field — either visible or hidden — from query params. For multivalued fields like Checkboxes, you’ve got 2 ways to format the params. Both are easy, but only one is correct.☺ →

Determine if a JS variable is a Marketo form object vs. HTML ˂form˃ vs. other form-ish things

My latest UTM attribution library — my 5th go-round after Conversion Path, NanoTracker, and a couple of private ones! — manages hidden fields on Marketo forms, raw HTML <form>s, →

Don’t start your LP domain with “ads” (i.e. ads.example.com)!

Some things you only learn at the School of Hard MOps. →

The rarely needed (but still important) “offSuccess” un-handler

Forms 2.0 events (onSubmit, onSuccess, onValidate) have a key difference from pure DOM events (<form> submit, <a> click, etc.). →

FlowBoost can check if a Data Value Change was a meaningful change, or just a case change

Is a change from “SANDY@EXAMPLE.COM” to “sandy@example.com” worth triggering on? Yeah, didn’t think so! →

Manage form field visibility based on Marketo segmentations

Hide a field for customers, show a field only to resellers, and so on — without creating multiple forms. →

To use Marketo {{lead.tokens}} in JS, output them into an HTML element, then read them back

IMO, deeply understanding several text encodings is better than superficially knowing multiple languages. Here’s a case where using the wrong encoding can be bad or… really bad. →

Automatically update images in Google Docs-based documentation

This post isn’t martech-specific. But it applies to MOPS process guides, so figured it was worth sharing. →