Safely embedding plain-text data in a Rich Text {{my.token}}

A brief addendum to the JSON {{my.token}} post. Sometimes, you might want to store just text (like comma- or pipe-delimited data) inside a data block.

Adding a download passcode to a Marketo form

Wouldn't it be nice to give people — say, tradeshow attendees — an instant download passcode? The code lets VIPs download an asset instantly, while others get it via email.

Don't call a Marketo LP an “External URL” even if it sort-of-works

When choosing a Thank You/Follow Up URL (wish there were only one term in use!) Form Editor presents 3 largely self-explanatory options: Choosing Landing Page will give you a

A strange way to break the Guided LP Editor

I occasionally go to extremes with the Marketo UI, hacking the Guided LP Editor itself. Crazy moves like that can accidentally break UI features, but that's to be

In Visibility Rules, “Contains” means a regular expression, not a string

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

This isn't a Velocity post, and yet it is

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.

Selectively track Marketo links and opens based on lead opt-in (think GDPR, o’course)

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.

Velocity ${formal.notation} invites syntax errors: use it wisely

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.