If someone recommends “Request Token Encoding: None” in a webhook, always push back
Using “None” for POST payloads usually means something else has gone terribly wrong. →
Help! My Velocity {{my.token}} previews correctly, but I can’t approve the email
At the moment of approval, fields on the $𝚕𝚎𝚊𝚍 object are empty strings (meaning "", not 𝑛𝑢𝑙𝑙). Your code needs to deal with that gracefully. →
Careful with native NodeJS fetch() in serverless setups (with any API, not just the Marketo API)
Reminder (if you needed one) that newer doesn’t mean more predictable. →
How an “unintrusive” 3rd-party tracking script caused duplicate Marketo form posts
Gotta love devs who don’t know Marketo but say “Just drop it in, trust us.” →
Have you no sense of DNS latency, sir, at long last?
Troubleshooting slow-loading email images reveals a classic culprit. →
Yes, you can use client-side {{ variable }} syntax (AngularJS, LiquidJS, Mustache, etc.) on Marketo LPs
Marketo uses both ${ } and {{ }} syntax internally, which makes mixing in other template languages tricky. But there’s always a way. →
Without checking SFDC Is Deleted, you don’t know if someone’s currently synced to SFDC
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? →
See quoted "{{ variables }}" in a template that’s generating JSON? You’re probably seeing a security hole
If you claim you’re sending JSON but the letters 𝚓-𝚜-𝚘-𝚗 don’t appear in your code, you’re in danger. →