A couple of (not at all rare!) situations where enabling Marketoโ€™s built-in reCAPTCHA breaks forms completely

If only such things were documented, right? Sigh.

Critical: Update to SimpleDTO 2.0 (the latest Form Pre-Fill JS) for compatibility with the latest Chrome & Edge

Act now to keep the magic alive. Upgrading from SimpleDTO 1.0 to 2.0 is super simple.

Achieving true round-robin (not random) assignment with FlowBoost

A ๐‘…๐‘Ž๐‘›๐‘‘๐‘œ๐‘š ๐‘†๐‘Ž๐‘š๐‘๐‘™๐‘’ step wonโ€™t cut it for lead assignment, since it can assign 2 or 3 people in a row to the same rep (by definition!). FlowBoost can handle it.

Extracting Smart Campaign/Smart List IDs from a ๐˜œ๐˜ด๐˜ฆ๐˜ฅ ๐˜‰๐˜บ XLS export

If you merely tolerate Excel, as I do, you want to make the export format compatible with other apps & dbs.

The scheme name of an Authorization: header (โ€œbasicโ€, โ€œbearerโ€, etc.) is case-insensitive. Somebody tell Calendly.

Sure, just enforce case-sensitivity overnight in defiance of the HTTP Authorization standard. What could go wrong?

When an eฬ is not an รฉ: about Unicode Precomposed vs. Decomposed characters (and why they matter)

Youโ€™ll never look at string equality the same way again. Includes a workaround for Marketo forms, but covering the rest of the stack is up to you.

An emergency workaround for app-๐‘›๐‘›๐‘›๐‘›.marketo.com form embeds after next weekโ€™s Marketo URL change

Canโ€™t shake the feeling that hundreds of Marketo users (and thousands of forms) are gonna break on August 1st. Hereโ€™s a workaround to make sure you escape form doom.

If youโ€™re still loading form embeds from app-๐‘›๐‘›๐‘›๐‘›.marketo.com, theyโ€™re gonna break on August 1st, 2023

IMO, Marketo is dangerously downplaying an upcoming change to LP/asset/form URLs. Make triple-sure your embedded forms arenโ€™t affected.