SanfordWhiteman

No matter how tempting, never do this with Marketo string fields:let jsVar = "{{lead.Some Field}}"; Why? Because {{lead.tokens}} are HTML-encoded, not JS-encoded. That is, they’re only supported in text content, like so:

You did the right thing: you reduced 100s of unmaintainable forms to a handful of global forms. You use native Visibility Rules to show/hide fields based on user input. Then your boss throws a curveball: “Can we show different fields if we already know somebody’s segment(s)?” Uh-oh. Segmentations ar...

Using a Google Doc to document internal processes (or external product docs, if you’re really daring) has the big plus of familiarity. Most everything else, IMO, is a minus — which is why docs-focused platforms exist! But one minus you can at least work around is that images embedded in a Doc won’t...

The hard part of email design is cross-client compatibility. Enhanced effects work in some web and mobile clients, but you need graceful degradation to HTML 3.2-era stuff, gotta have VML for Outlook desktop, etc. Identifying email clients is easy-ish after a person opens an email, but what about bef...

On a recent Marketing Nation thread, a developer had questions about the Get Folders API endpoint, one of Marketo’s paginated endpoints that returns folders in batches of (up to) 200: While paging through /rest/asset/v1/folders.json using the offset parameter, we are seeing duplicate folder ids in l...

A long way back, you learned that direct links to static assets (like, say, a PDF) won’t be tracked by Munchkin. You should instead have a central Redirector LP that hooks up the Munchkin cookie before flipping to the target asset. Later, I showed how to instrument Munchkin so an event fires as soon...