MKTO Only Records and Duplicate via Salesforce | Community
Skip to main content
M
mzzee
Level 4
May 25, 2021
Solved

MKTO Only Records and Duplicate via Salesforce

  • May 25, 2021
  • 1 reply
  • 1839 views

Hey!

 

So I'm realizing that we have quite a duplicate problem. We regularly upload records in Marketo only, where we intend to nurture them until they take an action that will eventually get them sync'd to SFDC.

 

However, many times our sales team will create the same record in SFDC. This causes there to only be 1 record in SFDC, but now we have duplicates in Marketo.

 

Is there any way to prevent this from happening or having the SFDC-created records automatically merge with the MKTO-only record?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Katja_Keesom

Without knowing a little more about your scenario, the issue could well be with the fact that the two entry methods have a different unique key. Records coming from SFDC are matched by their unique SFDC id, but a list upload will use email address as the unique key. This means that the scenario where the SFDC record exists first will work fine, as the list upload will recognize the existing record and update it. The other way around however will cause issues, because the SFDC sync will not recognize the preexisting record from the list upload (as it has no SFDC id listed).

 

What the best way would be to manage this depends on a lot of things, like the amount of duplicates and your internal processes (and to what extent you can change these). It ranges from a manual cleanup to a redesign of your process to software that can automatically manage these flows for you.

1 reply

Katja_Keesom
Community Advisor and Adobe Champion
Katja_KeesomCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
May 26, 2021

Without knowing a little more about your scenario, the issue could well be with the fact that the two entry methods have a different unique key. Records coming from SFDC are matched by their unique SFDC id, but a list upload will use email address as the unique key. This means that the scenario where the SFDC record exists first will work fine, as the list upload will recognize the existing record and update it. The other way around however will cause issues, because the SFDC sync will not recognize the preexisting record from the list upload (as it has no SFDC id listed).

 

What the best way would be to manage this depends on a lot of things, like the amount of duplicates and your internal processes (and to what extent you can change these). It ranges from a manual cleanup to a redesign of your process to software that can automatically manage these flows for you.

    Terms & ConditionsAccessibility statement

    Loading footer...