#throw() an error from Velocity to emergency-stop a send
Revisiting the “Poison Pill” concept from years ago, and providing a better error-thrower macro. →
Revisiting the “Poison Pill” concept from years ago, and providing a better error-thrower macro. →
You’ve heard of GA’s ‘hitCallback‘ and GTM’s ‘eventCallback‘... now, meet Munchkin‘s ‘munchkinHitEvent’! →
We’re doing it live! (Because I’ve always thought there were too many precise steps for a blog post.) →
Todd Sprinkel’s a friend and tech whiz (I subscribe to his newsletter, if that tells you anything!) and he just came out with a FlowBoost-related post I can’t →
A checked Checkbox doesn’t always mean String “yes”/Boolean true. Depending on your form logic and db schema, checked may correspond to “no”/false in the database, while unchecked is “yes”/true. The Forms 2.0 library assumes checked means “yes” but with some crafty code we can flip it. →
Sometimes, even I have to admit that Marketo Forms being jQuery-based — as opposed to using vanilla JS — makes custom/hacky behaviors easier to implement. →
The worst attempt at form anti-spam prevention I’ve seen yet. →
Memory matters: if your Velocity code is inefficient and/or too obscure to be optimized, you can slow or even crash your Marketo instance. →