Next Thursday, I’m revealing a top-secret email template trick at a free Adobe event in NYC
If you’re around here, you should be there. →
URL-encoding unsupported characters to avoid major data loss, in a few different languages
Using our old friend, URL encoding (a.k.a. percent encoding) to avoid the pretty shocking data loss described in the recent post. →
Yet another input mask tweak: allow only Latin-1 letters and punctuation — but not numbers — with no fixed length!
Love encountering hyper-specific validation rules like this! And they make sense when legacy-ish systems need to ingest Marketo data. →
In Marketo String/Text fields, surrogate pairs MUST be URL-encoded, and you SHOULD encode line breaks
This is likely a surprise: you can permanently lose data just by including certain characters in fields. And it’s not just those characters that disappear, it’s everything after them, too. →
Incrementing FBCounter multiple times in a single call
When you offer event registrants a +1 (or +10) you need to update your count accordingly. →
Velocitip: Show a string’s Unicode codepoints
Nothing wrong with getting nerdy in Velocity, especially when small Velocity field differences make your head spin. →
Hashing or encrypting Marketo data for export (using FlowBoost)
We should all be concerned about sending PII to 3rd parties. Some partners explicitly say “Hash those emails, we don’t wanna see/store that.” And even if they don’t, let’s take the initiative. →
Using mktoBoolean variables to conditionally load ˂script˃ and ˂link˃ tags
Safely roll out new scripts and styles with a go-back switch for emergencies. And it’s bog-standard HTML, no comment hacks. →