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. →
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. →
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). →
In the most recent Velociteaser [https://blog.teknkl.com/velociquiz-split-and-contains-why-does-it-work] I challenged readers to explain why certain Velocity code works instead of — as a datatype mismatch suggests — throwing a fatal →
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. →
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. →
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. →
Once more into the breach of Excel, my least favorite app... and yet one I can’t quite eliminate from my life. →