Email address, IP address match, but not the same lead...

[Colby_Dix]

So I was alerted to this this a.m. by our Salesforce supprt tech. Basically, we have a dummy address that we use (none@ourdomain.com) for leads without an email address that we still want in SFDC (our SF instance requires an email for leads) and this address is used all the time. Fine fine.

Today we had a lead get updated that was clearly not a match in terms of the names and info (different states, names etc;) but because it originated from the same IP address, MKTO updated the older lead with the newer leads info.

Does this make sense? Is this by design? Or am I wrong in assuming the same email/IP combo is the culprit?

Thanks!

[Josh_Hill13 · Accepted solution]

Marketo dedupes by email address. So if you have a bunch of leads assigned to none@ourdomain.com, they will be considered matching dupes regardless of IP or Name. This assumes the leads come into Marketo FIRST.

So if you could have a situation where you create leads in SFDC with that email, those get synced to marketo. Then someone is uploaded to Marketo with that email, gets deduped against one of the emails and syncs back. Usually Marketo does this with the most recent leads.

I would caution against syncing leads from marketo to SFDC w/o an email (which you realize), but just not even pass them over because of this risk. Or maybe have a trigger in SFDC that adds a unique # to the lead's email.

[Colby_Dix]

Makes sense, and yeah, this is a new situation where indeed the 'new' leads were being created via MKTO form, so that's why the error came about. 

We had been adding the 'none' email  for sometime when leads came in w/o emails in SFDC, but never as such in MKTO.

Thanks!