I've been modifying forms based on inferred country — GDPR/CASL-related — and that means checking if an IP address is in a known range. First, I'll show that what you think of as an "IP address" is probably not-quite-right, then how JS Array methods can help out with a necessary conversion. →
You can store JSON blocks as Text {{my.tokens}}, then embed the tokens in LPs for advanced dynamic content. Making JSON maintainable in the Marketo UI takes a little trick. →
A brief addendum to the JSON {{my.token}} post. Sometimes, you might want to store just text (like comma- or pipe-delimited data) inside a data block. →
Wouldn't it be nice to give people — say, tradeshow attendees — an instant download passcode? The code lets VIPs download an asset instantly, while others get it via email. →
When choosing a Thank You/Follow Up URL (wish there were only one term in use!) Form Editor presents 3 largely self-explanatory options: Choosing Landing Page will give you a →
I occasionally go to extremes with the Marketo UI, hacking the Guided LP Editor itself. Crazy moves like that can accidentally break UI features, but that's to be →
Little-publicized, to the point that even Support [https://nation.marketo.com/ideas/9501] isn't in the loop: the Visibility Rule Contains operator does allow multiple values. The Contains →
Just when you thought variables not working in the Text version of emails was a mostly harmless detail, you find it has wider consequences that are firmly buggy. →