Marketo field limits in the real world, Part III: *Numeric strings* are not numbers

Spinning this off the earlier Part I (on number types) because it's an equally important topic. Not necessarily a rivetingly interesting topic, but since some of you are trying to

Shuffling and rotating output in Velocity

I wrote earlier about using Velocity's $math.random() for basic A/B testing. Here are some other things you can do in the same vein by referencing Java's java.util.

Form Pre-Fill. External sites. No limits. You're welcome.

And any form, not just Marketo embeds. Finally, my long-mysterious method is open source!

More things to unlearn from the Marketo Script Editor

There's another area where Marketo's starter Velocity code is a bad look.

Code Anatomy: Convert a dotted IP address to decimal

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.

Safely embedding JSON data in a Rich Text (as opposed to Text) {{my.token}}

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.

Safely embedding plain-text data in a Rich Text {{my.token}}

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.

Adding a download passcode to a Marketo form

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.