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.
Right, although Marketo itself can combine Lead and Contact IDs (including tracking conversions and merges on the SFDC side) when using the API you'd have to use a separate request...
A reasonable request, but you can’t enforce this via the UI. You can build a custom import app (honestly it’s hard to believe many companies can survive without one!) that uses the...
Also, it doesn’t make a ton of sense to look up using the SFDC ID if you can use the Marketo Person ID.
This ID is of course set from the very moment they call the webhook, no nee...
You can’t update people using a direct lookup on sfdcId (that’s the API name for the computed field we think of as “SFDC ID“).
If you know the person’s SFDC Type (easily derived f...
I saw on the dynamic content guide page that it only works for triggered emails, not batch...
That’s not accurate. The note you’re referring to is specifically about variables ($...
This seems like a great opportunity for the Forward to Friend feature, since you have a captive audience (salespeople) who you know will use it.
(Typically, getting end users to a...
This can be done quite easily using a webhook-compatible service that swerves back and calls the REST API. It can even merge the leads together programmatically. But there’s no mag...
You’re likely running into known behavior of the Velocity Introspector when reusing using the same $variable.
Try it like this instead (also fixing up some variable names that we...