A Pride flag (or any striped flag!) effect for Marketo forms
Is 3-D the future of forms? Not sure about that, but this was a fun experiment with more to come. →
A global YouTube Player LP is smart — just don’t let it get hijacked
Having one global Media Player LP (and global Asset Download LP) is a real timesaver. Just make sure they’re only useful to you, not to anyone else! →
Simulating a DateTime {{my.token}} (not Date) using an undocumented method
You wouldn’t know it from the Marketo docs, but a Text {{my.token}}, formatted the right way, can serve as a DateTime {{my.token}}. →
Loading Munchkin in an IFRAME (when forced by a feature-limited app)
Restrictive SaaS apps — think community platforms — can frustrate our analytics desires by only supporting the 800-pound gorilla (GA) or an IFRAME. But all may not be lost. →
Your IT team is wrong: there’s no reason to expect https://▁▁.mktoweb.com to open in a browser
The word of a MOPS veteran ⋙ pushback from an IT newbie. →
Localizing Global Form Validation Error Messages
Global Form Validation Rules are a big win, but Marketo left something out. He’s how to patch it over (and learn some cool postMessage and Ajax tricks in the process, if you feel like it). →
Once you manually Q-encode an emoji in a Marketo Subject, you must manually Q-encode other non-ASCII chars, too
My classic “Yes, Virginia” post proved there’s no barrier to using emojis in Marketo, as long as you manually Q-encode. But there’s a quirky side effect. →
Getting FlowBoost usage stats with FBSelf.usage
You can now check daily/monthly API call usage from inside a FlowBoost webhook, then send alerts straight from Marketo. →