Another way tracked links will break (hard) if you don’t consider %-encoding
There are so, so many ways to break links. I’ve seen more encoding disasters than most, but this one was new to me. →
Find the end of the current quarter and/or previous quarter in Velocity
More dynamic date magic that can be done simply using Velocity and Java (after a little head-scratching). →
Sure, multiple query params with the same name are allowed, and Auto-Fill acts accordingly... but what does “accordingly” mean?
A subtle mistake in a link sent to 100,000 people was about to wreak havoc on attribution. Here’s how we avoided that with an emergency JS intervention. →
Rescuing Landing Pages from a mass placeholder-image-loading catastrophe
Chances are your site is only usable if multiple 3rd-party services are up and running — part of the cost/benefit of not building stuff in-house. But you definitely don’t want to rely on seemingly developer-only services being up! →
Phone numbers aren’t actually numbers
If one group is making guesses about another group’s datatypes, your project wasn’t ready for go-live. →
For multivalued Marketo fields, consider URL-encoding instead of JSON or semicolons
There’s no One Best Way™ to store complex data. To find the best fit, consider what — and who — will be doing the encoding and decoding. →
So You Think You Can Unicode, Quiz #2
> Update 2022-03-18: The prize goes to Shivam, who DM’d me the correct answer: 31 bytes. I’ll explain in the next post! Another encoding-related quiz, this time with →
Two DKIM records (for the same selector) will break stuff. Pretty much all the stuff.
Last night we heard from a user that 90%+ of their Marketo emails were flagged as spam. They’d only made a minor DNS change — or rather, what they thought →