Marketo click tracking only works because 2 JavaScript bugs cancel each other out

Code that works by luck rather than by design? Yikes. A brief code review would’ve caught this one. →

Deleting the non-deletable: clear an overridden {{my.token}} using the Marketo API

You don’t need to accept “Token is already in use” as a permanent condition. →

Why you 𝒅𝒐𝒏’𝒕 need to check if GTM’s window.dataLayer was blocked by an ad blocker

An exceptional case where you’d think code isn’t resilient, but it mysteriously is! →

Check out my colleague Jo Pitts’s blog, too

Jo & I are kindred spirits (and collaborators) and the revived MoTaM blog is highly recommended. →

Using a Marketo form to register people in a Teams webinar (via FlowBoost)

You can’t stop Teams, you can only hope to integrate it. →

Using the SFDC Type in Dynamic Chat audience criteria

Finally opened the hood on Adobe Dynamic Chat, revealing a familiar mix of overall coolness + unexpected quirks. As with everything Marketo, workarounds abound. →

Using native HTML ˂dialog˃ for modal Marketo forms instead of legacy lightbox()

Forms 2.0’s lightbox() is fine (if misunderstood) but unless you’re supporting IE, it’s time to move on to the new stuff. →

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