Spinning this off the earlier Part I [https://blog.teknkl.com/real-world-marketo-field-limits-1-integers] (on number types) because it's an equally important topic. Not necessarily a rivetingly interesting topic, but →
I wrote earlier about using Velocity's $math.random() for basic A/B testing [https://blog.teknkl.com/lightweight-a-b-testing-in-velocity/]. Here are some other things you can do in the →
And any form, not just Marketo embeds. Finally, my long-mysterious method is open source! →
There's another area where Marketo's starter Velocity code is a bad look. →
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. →