Adding placeholder text to a Marketo datepicker
Buried in my CodePen demos are some techniques that never got their own blog post. Here’s one that deserves a promotion. →
Reversing a data mangling disaster with Get Lead Changes + a regex trick
After a data disaster, grabbing a backup can be the easy part: Get Lead Changes should be your go-to. It’s *restoring* that’s tricky, especially if only one narrow type of change is a “bad change.” →
No, Marketo tracked links are not “invalid HTML”
It’s Marketo vs. a venerable ISP with an ancient-seeming webmail UI. Don’t trust either party’s word — trust the HTML standard. →
Randomly shuffling the order of checkboxes to shake off bias
Worried that leads are just clicking the top checkbox instead of thinking things through? Shuffle ’em up every time! →
Don’t (yes, *don’t!*) worry about “garbled” characters when opening JS files directly in your browser
Being paranoid about encoding helps avoid uncomfortable post-mortems. But here’s one type of apparent encoding bug that’s actually a false alarm. →
Why Marketo LP Domains and Domain Aliases can’t have an underscore
When you try certain settings, SaaS apps may give a weak “Please don’t?” instead of a hard “NO!” Marketo does the right thing here for technical reasons, driving home that underscores shouldn’t be expected to work across your stack. →
You probably don’t know how easy it is to parse email addresses using FlowBoost
And that’s my fault. This year’s resolution was to document more of FlowBoost’s secret functions — the “macros,” if you will, that are built-in so you don’t →
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. →