The rarely needed (but still important) “offSuccess” un-handler
“We’re seeing duplicate GTM Data Layer updates for a single Marketo form fill,” read the trouble ticket. “Sometimes even 3 or 4 updates.” My mind went to adding multiple →
Don’t start your LP domain with “ads” (i.e. ads.example.com)!
Some things you only learn at the School of Hard MOps. →
FlowBoost can check if a Data Value Change was a “real” change, or just a case change
Marketo uses exact string comparison (case-sensitive and accent-sensitive) to determine if fields have changed. Overall, this is good: otherwise, we’d never know if enrichment/normalization APIs were working. Problem: →
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. →
Gain instant lead insight with a DNS MX lookup
Identifying email client(s) is easy enough after people open an email, but what about before? →
Alert when your FlowBoost API key runs out of monthly calls
Know when it’s time to upgrade. →