You probably know that email addresses are teeeeeechnically case-sensitive but, like most sensible creatures, you treat them as if they’re case-insensitive. (As Marketo Smart Lists obviously do!) Wouldn’t →
💡This code does not work in any version of Internet Explorer, as it relies on URLSeachParams and Custom Elements v1. An earlier post showed how to append form field values →
Clearing the Munchkin cookie does one thing, and does it well. But chances are you want this other thing, too. →
Velocity is in essence a way a more “sugary” way to write Java, and has almost nothing in common with with JavaScript. But even I forget sometimes and think it plays by JS rules. →
Marketo gets curiously angry when you try to add <style> elements in the Rich Text Editor, though such elements can make strategic sense. They don’t apply the same punishment to <script> elements nor custom elements, so that gives us a workaround. →
Call it an unwelcome feature, call it a bug, call it a security vulnerability. Whatever you call it, here’s how to call it off (mostly). →
Phone numbers can take many formats (Marketo, like most apps, treats them as strings under the hood). If you want to use a standard format in outbound emails, Velocity can help. →
Native Visibility Rules can’t manage the Submit button state, but a little custom JS can. →