Can't believe someone other than me has thought about cryptographic techniques in Marketo! But in this recent Nation thread [https://nation.marketo.com/thread/46457-is-it-possiblefeasible-to-sha-256-hash-users-email-addresses-in-marketo%5D] , a user →
The Marketo Forms 2.0 Email type — just like an HTML5 <input type=email> — won't throw an error on "sandy@gmail" (with no ".com"). But that's not a bug. →
Sorta surprised no one else has come up with this yet (that I know of). Here's a quick way to let your users switch between 2 stylesheets: < →
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. →