Little-publicized, to the point that even Support [https://nation.marketo.com/ideas/9501] isn't in the loop: the Visibility Rule Contains operator does allow multiple values. The Contains →
Just when you thought variables not working in the Text version of emails was a mostly harmless detail, you find it has wider consequences that are firmly buggy. →
GDPR and related regulations call for some fancy footwork with activity tracking. Leads may be members of the same program, set to receive the same email... but many have opted-out of tracking, while the rest agreed to be tracked for the greater good. →
There are 2 ways to access references (i.e. variables) in Velocity: simple and formal notation. Use simple unless you're absolutely positive that you must use formal. →
The person's Marketo ID (oh-so-useful for building links and such) isn't available in the Velocity field tree, but you can still access it. →
You've seen before that the Forms 2.0 input mask plugin can be tweaked to do some more elegant stuff. Here are a few more ways to push the envelope. →
Is bad code a teachable moment? I keep thinking it is. Might just be an excuse for another rant, though. →
> This tip is used in this post [https://blog.teknkl.com/selectively-track-marketo-links-based-on-lead-opt-in-gdpr] on sending tracked or untracked links based on each lead's “OK to track me” setting. →