Microsoft “New Outlook” strictly enforces RFC 5545, potentially breaking ICS file generators (though not Marketo’s)

Violating the old Never Rewrite From Scratch rule (which, let’s be honest, is sporadically enforced) Microsoft created New Outlook in 2023. So far, it’s been a rocky rollout, →

Returning 𝚏𝚊𝚕𝚜𝚎 from an 𝚘𝚗𝚂𝚞𝚋𝚖𝚒𝚝() listener doesn’t stop submission — or do anything at all!

A user had buggy 3rd-party JS causing forms to be submitted 2x. Unable to find the root cause in their stack of plugins, they tried a desperate fix: add an →

A bunch of “Unsubscribe Email” activities for different emails, 5 minutes apart? That’s Gmail’s Manage Subscriptions feature

Read between the (log) lines and you realize Gmail is hitting every List-Unsubscribe link, from first to last. →

A crazy way custom forms JS can cause “Submission failed,” with “checksum invalid” in the details

The 20th field added to a Marketo form is special (yes, only the 20th!). Combine that obscure factoid with bad custom JS and you break the form. →

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? →