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

Nobody asked Microsoft to fix this, though I guess it’s hard to object. Meanwhile, the rest of the iCalendar world is more generous. →

Returning false from an onSubmit() listener doesn’t stop submission — or do anything at all!

Marketo forms use proper <form> and <input> elements, but they don’t submit like vanilla HTML forms. (Also: come on bro, test your code.) →

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