Consider decoding URLs if you’re just storing them for attribution
URL-encoding isn’t something you just do (or hope someone else does for you!) and forget about. It’s required in only one case, and outside of that, might be better off undone. →
Why “Grab Images from Web” may show an error or return partial results
Just a few notes on why this Marketo “extra” isn’t always usable. →
Here’s why your “Autofill from Referrer Parameter” setup stopped working
Historically, browsers shared a disturbing amount of information across sites, with no way to disable sharing. In the past decade, those features have gained on/off switches, and finally in late 2020 (!) they’re off by default in in Chrome, heavily impacting Referrer-based UTM tracking →
Re-enabling the “onSubmit” event when Known Visitor HTML is on
Known Visitor HTML is simpler than a standard Marketo form — to a fault. Here’s how to re-enable the full JS API in KV HTML. →
Interesting li’l bug in Email Editor » Edit Code » Download HTML
Alas, no solution for this one (it’s a bug in the Marketo app). But thought the cause was interesting. →
Using a ${mktoVariable} on the <html> element itself
Marketo’s <meta> preprocessor tags — used to declare the different types of ${mktoVariable} — may look like standard <meta> tags, but they’re actually more flexible, DOM-wise. →
HubSpot form events have a security vulnerability if you use their boilerplate JS
I spend very little time in HubSpot, but it’s always fun to find a vulnerability in a major platform. →
Add-on to “Avoiding the dreaded ‘Invalid Image URL’ error with tokenized assets”
An addendum to the earlier post [https://blog.teknkl.com/fixing-invalid-image-url-tokenized-links/] about using tokenized image URLs like https://pages.example.com/rs/123-XOR-456/images/{{Lead.Sales Owner Email Address}}-med. →