Hi Tazzy, Greetings! Based on your post on community "Salesforce Marketing Cloud to Marketo Migration". I would like to assist however, I have few queries before we can share the nearest Ballpark figures with you. You are currently moving from B2C to B2B platform which means direct integration may not be possible maybe custom built API will be used including the flat file system. Also, can we have some understanding of the volume metrics of the things you need to migrate as there's a possiblity that you'll probably be needing the data enrichment, data cleanising also. So If I have some details I might be in better position to share some Ballpark figures. Looking forward to your response. Thanks Tanush B
... View more
You certainly don’t need to be an admin to use the API — that would be a catastrophic security flaw. (The whole idea is outside apps can use specific API endpoints, if they all had to be admins that would be... bad!)
You do have to have an API-only User in addition to your regular interactive user, however. You don’t use the same login for the UI and API. And of course there needs to be a Launchpoint service (Custom type) set up for you. The client needs to do more to set you up. Sounds sort of like they haven’t used the API before?
... View more
From my understanding Marketo will create a duplicate of any records where an email does not currently exist.
That’s not exactly true.
Multiple form submissions with no Email Address field from the same Munchkin session — i.e. associated Munchkin cookie — will be merged into only a single lead.
That’s because the Munchkin cookie is a “strong associator”: if someone already has an associated cookie, in the absence of stronger input, Marketo will continue to connect activities to the same lead.
However, it is true that across different Munchkin sessions, multiple form fills with no Email Address will create multiple new leads.
Now, to your question about looking up leads (I prefer to not say “dedupe” here) by another field like Mobile Phone. First, it’s not possible to look people up directly by that field, since it’s a system field. This is somewhat confusing, but easy to work around: you create a custom field Mobile Phone Lookup and then always mirror the Mobile Phone value into that field (e.g. using a trigger campaign on New Person and Data Value Changes).
Now, you’ll be able to use Mobile Phone Lookup as a lookup field via REST API. Even though dupes will exist for a moment after a form fillout, you can immediately call a webhook-compatible service via API that will loop back and merge together all people who have a matching phone number, resolving the problem promptly.
... View more