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.
The REST/SOAP APIs wouldn't be appropriate for real-time use anyway. They're for batch operations.The problem with your situation as-is is the lead's web activities are going to re...
You should be using the Marketo Forms Editor to build out your forms as much as possible, and complement that with the Forms 2.0 API. What's the reason you're manually building out...
"__c" just means "custom." It's perfectly harmless. Like Salesforce and other platforms, Marketo separates built-in fields from custom fields with a special suffix (some platforms ...
Even better/in addition, if there were an official way (rather than a hack) to customize the first Visit Web Page from Munchkin::init, then we could code up whatever we want.
Hey guys, here's a "teaser trailer" of something I was working on this weekend that I'm going to publish in a few days: Bitlify TT 01This'll give a leg up for creating Bitlinks wit...
If you need to add data from the document itself before logging Visited Web Page activity, I recommend adding it to the hash before you initialize Munchkin:var productMeta=document...
There are three major ways to use lead info within a page:Embedding tokens directly into a JS function call: _ga.push( {{Lead.Salary_Level__c}} )Embedding tokens into a JS object o...