Sync records, same email created one in Marketo and other in SF | Community
Skip to main content
RaulEr
RaulEr
Level 4
June 15, 2023
Solved

Sync records, same email created one in Marketo and other in SF

  • June 15, 2023
  • 1 reply
  • 843 views

Hi community,

 

I have this scenario where a lead is created after a form is completed, but also, when the form is completed it redirects to a Calendly link that creates a record on Salesforce. E.g. At 10 am it creates a record in Marketo, then at 10:05 am a record is created in Salesforce (same email and all info) and after sync, we end up with duplicates.

 

Is there a way to tell both Marketo and SF that they are the same 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 SanfordWhiteman
Is there a way to tell both Marketo and SF that they are the same record?

No, because they literally are not the same record. They may represent the same person at a business level, but Marketo will never assume that for you.

 

I recommend integrating Calendly with Marketo instead. That way there is one entry point, which is far more manageable.

 

You can also call the Marketo Merge Leads API from a webhook-compatible service for well-known cases like this. But bear in mind a full-fledged automerge service needs to take a lot more into account.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
Level 10
June 15, 2023
Is there a way to tell both Marketo and SF that they are the same record?

No, because they literally are not the same record. They may represent the same person at a business level, but Marketo will never assume that for you.

 

I recommend integrating Calendly with Marketo instead. That way there is one entry point, which is far more manageable.

 

You can also call the Marketo Merge Leads API from a webhook-compatible service for well-known cases like this. But bear in mind a full-fledged automerge service needs to take a lot more into account.

    Terms & ConditionsAccessibility statement

    Loading footer...