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 →
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. →
Don’t settle for sloppy: here’s how you set up auto-updating and time-zone-accurate {{my.tokens}} to output the current year. →
You can easily transplant UTM-based attribution data from one page to another — as long as the source page trusts the target enough to pass the (full) referrer. →
In Marketo, tokens are critical to keeping your head on straight. But in some parts of the UI, what you think is special {{token.notation}} is just plain ol’ curly braces. →