The Marketo REST Asset API returns invalid ISO 8601 DateTimes
Honestly not sure how this bug exists — you’d think Adobe would use a Date library that prevents it from happening. →
Honestly not sure how this bug exists — you’d think Adobe would use a Date library that prevents it from happening. →
Never let them tell you Velocity is an overnight learn. →
Something for my fellow push-it-to-the-limit Marketo pros. Discovered this when sending a ton of debug info back from a FlowBoost webhook. (Not to map that info to Marketo fields, only →
Apparently, people still try this. The business case might be okay (though old-fashioned) but it’s technically doomed. →
Outdid myself with this one, I must say. Already using it with multiple clients — plus running the code on random websites out of curiosity. Think you’re gonna love it. →
Marketo webhooks put all other webhooks to shame. But their configurability means a few more things to master. →
SFDC picklists and Marketo form checkbox sets become so-called “multivalued strings” in the Marketo db. But in the Marketo UI, they’re just strings that happen to have semicolons — there’s no native awareness of sub-values. FlowBoost, on the other hand, has full awareness and can do magic. →
It represents a lot of round-the-clock effort and isn’t advised for those who sleep. (Not sure if I hate or love how my headshot aligns with the frame!) →