Every Marketo field has a Friendly name, a Token name, a Form Field name, a REST API name, a SOAP API name, and a Velocity name — and they may all be different
Don’t be scared, but don’t make assumptions about any 2 of these being the same. →
A global trigger campaign to alert on interesting Program Status changes, with the new Status included in the alert
Marketo recently added a bunch of new {{trigger.tokens}} that can help reduce the number of nearly-redundant trigger campaigns, always a good thing. Some of the tokens are relatively “raw, →
Flip a Marketo form field between “Required” and “Not Required” at runtime
Build advanced form behaviors with this bit of JS. →
NYC MUG in-person talk and meetup: Thursday, 9/25
See you there? →
Extract “Firstname B. Lastname” from “firstname.b.lastname@example.com” using Velocity (with caveats)
Consider this a stopgap measure while you’re waiting for First and Last to be properly mapped. →
Custom Object tip: create a duplicate field if you’ll need to constrain a Date/DateTime to specific ranges
Reporting and filtering requirements can force a weird CO schema, but it works. →
You should probably be checking "isTrusted" in postMessage() listeners
The accepted way to secure postMessage() has a bypass you likely don’t know about, even if it’s not the hugest deal on its own. →
Check if the current pageview is associated with a Marketo lead (without using the ol’ hidden KV HTML trick)
Rendering a hidden form just to check if someone is associated is a waste of resources. Here’s how to check efficiently. →