SPF records can allow MAIL FROM:user1@example.com but deny user2@example.com (even if it’s rare)
Only old school SPF-heads have this kind of setup, but SPF *can* be per-individual-sender instead of per-whole-domain. →
Here’s the Hypersegmented template from today’s talk @ Adobe
You’ll probably want this code if you stayed awake. →
A long talk with Justin Norris on his new RevOps FM podcast
A big day: my first post tagged “podcasts.” →
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. →