A client recently asked about connecting Marketo to Clay and we were dismayed at Clay’s official docs: See how they recommend Request Token Encoding: None? That’s totally wrong, →
Knowing if the current pageview is associated with a known lead vs. anonymous is key to a lot of cool personalization. For example, you can build the equivalent of “If →
At the moment of approval, fields on the $𝚕𝚎𝚊𝚍 object are empty strings (meaning "", not 𝑛𝑢𝑙𝑙). Your code needs to deal with that gracefully. →
Reminder (if you needed one) that newer doesn’t mean more predictable. →
Gotta love devs who don’t know Marketo but say “Just drop it in, trust us.” →
Troubleshooting slow-loading email images reveals a classic culprit. →
Marketo uses both ${ } and {{ }} syntax internally, which makes mixing in other template languages tricky. But there’s always a way. →
You know some system fields in Marketo are more historical than current (looking at you, Email Suspended). But did you know SFDC Type and SFDC ID also fall into that bucket? →