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. →
Conditional content that only shows in View As Web Page mode
View As Web Page has so many superpowers over plain email, you almost feel like breaking the email HTML on purpose. →
Check if someone’s email is @ their website — i.e. is their work address — using FlowBoost
Marketo filters can’t do “field1 [ends with] @field2” but FlowBoost handles that easily. →
Filling hidden fields from utm_* params on Squarespace forms
Every time I’m forced to dip into other form builders, I miss Marketo forms. Marketo’s are not only more programmer-friendly, they also do things out of the box that require custom JS elsewhere. →
Is an email address that requires encryption (STARTTLS) a “valid email”? It depends
All email validation services fundamentally do the same thing: * look up the domain to see if it has an MX record * if it has one, connect to the MX and →
You’re probably overusing “&” in links
If a URL’s query params all start with “utm_”, no need to separate them with “&”. A simple “&” will do. →