Using a ${mktoVariable} on the <html> element itself
Marketo’s preprocessor tags — used to declare the different types of ${mktoVariable} — may look like standard 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 about using tokenized image URLs like https://pages.example.com/rs/123-XOR-456/images/{{Lead.Sales Owner Email Address}}-med.png — which throw an error →
Get all the fields in a Marketo instance, including their Descriptions
Yet another F12 Console hack to perform an export via the Admin UI (an export you can’t get any other way, including the API). →
February’s Brainteaser unteased: Here’s why that bit of Velocity code works instead of failing
In the most recent Velociteaser I challenged readers to explain why certain Velocity code works instead of — as a datatype mismatch suggests — throwing a fatal error. To recap, we had →
Accurately background-loading the MktoForms2 global object
Background-loading (a.k.a. defer-ing or async-ifying) MktoForms2 makes the non-form parts of your page more resilient in the face of network slowdowns. Here’s how to do it right. →
Brainteaser: Why does this line of Velocity code *work*?
Velocity uses under-the-hood magic to reduce (but not eliminate) fatal errors. Figuring out “Why does this work... when it kinda shouldn‘t?“ is vital for mastering the language. →
Running Subject Line AB tests with segmented Subjects
Some Marketo features aren’t compatible with Dynamic Content™ (stuff labeled “Dynamic Content” in the UI) but you can use simple Velocity to accomplish the same outcome. →