I'm a web, database, and network architect based in NYC, with specializations in the financial services, publishing, and SaaS sectors.
I build complex Marketo integrations for companies large and small... and can make Marketo forms and emails do things you never thought possible!
Check out my blog at https://blog.teknkl.com, which has Marketo-specific technical insights you won't see anywhere else, along with wider topics from my programming and systems work.
Certainly the client-side hidden form post is technically possible, since it doesn't involve server code at all (that is, if you didn't have a server you controlled, the server-sid...
Lindsay, the decision to use an API call for every form post was reckless. You can tell your engineering team I said that. I strongly recommend you change the architecture. You ca...
Jodie, the expression "trigger an email campaign" suggests you want to listen for Data Value Changed events. Thus the value needs to be some kind of Marketo field. While it's theor...
I'm talking about the DoS risk aspect in addition to the PII leakage aspect. With 10,000 API calls per day shared among all your integrations, you're taking a tremendous risk by a...
But the technique in that blog post creates a DoS vulnerability for your Marketo instance. A company with an understanding of risk -- if not security per se -- should reject that o...
It is still officially the case, for sure. There are, however, crafty ways to engineer this functionality. I demoed one of them at the NY MUG in August. If you want to know more ab...