If your stored URLs (in both URL and String fields) include the protocol — as you‘d assume they should! — that makes them non-trackable. Velocity can make ‘em trackable again. →
You might think choosing an LP subdomain (pages.example.com, get.example.com, etc.) is just a branding thing. But there are a few hostnames you must not choose, for quirky technical reasons. →
If a SaaS app lets you store certain characters in a field, your offline data warehouse (or data lake, or archive, or whatever) must support those same characters, no matter how rarely used. →
Use this little bit of JS to pass submitted form values across sites, from a Marketo form on Domain A to a Thank You page on Domain B. →
If you’re storing IRIs — as I previously advised for readability and compactness — you might someday need to turn them back into URIs. Velocity can do that. →
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. →
Just a few notes on why this Marketo “extra” isn’t always usable. →
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 →