SanfordWhiteman

Say you have an LP section like this:

tl;dr: if a URL’s query params all start with utm_, you do not need to separate them with &. Use the simple &. Using & when it’s not required is harmless. But it’s not really best practice, since it makes links harder to build by hand and harder to read. On the other hand, if you use params other th...

Marketo uses exact string comparison (case-sensitive and accent-sensitive) to determine if fields have changed. Overall, this is great: otherwise, we couldn’t use enrichment/normalization APIs! One side effect is not-quite-real changes to fields like Email Address (which teeeeechnically is case-sens...

The sheer audacity of 3rd-party form trackers (conversion pixels, enrichment services, attribution libraries) is amazing. “Don’t worry about telling IT,” they’ll say. “It has zero side effects, just drop it onto every landing page.” Now if their code is correctly detecting and using the Marketo Form...

Standard ask: “Can we ‘prime’ a form with selections based on the query string?” That is, if the query string includes “GC5000 series” and “GC3000 series,” check those boxes automatically, letting the user change those selections if desired: We sure can, with a few lines of JS! The question is what ...

Much of MOps is explaining why things that seemingly shouldn’t happen (a) clearly are and (b) with good reason. Case in point: it’s possible for a Contact’s fields to stop updating from Salesforce ➞ Marketo and vice versa, while that Contact’s new campaign memberships continue to sync to Marketo! Wh...

“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 onSuccess listeners. Sure enough, they had a setup like this:function gtmAfterSubmit(submittedValues){ dataLayer.push({ event:...