Sean_Richards

Also to confirm. I tested the conversion being done from RingLead in batch, Ringlead, single records one by one, and Manual conversion within SF and was able to trigger the issue in all three scenarios.

Hi Justin,Thanks for sharing this information. I could test this theory for us all today. So I disable my sync, perform a bunch on Lead Coverts, then turn the sync back on, then we'll see if I catch any irregular merges. Stay posted!This is linked to these threads as well:https://nation.marketo.com/...

Also, this might not occur with the Dynamic's sync. I believe it's the way the sync to SF is coded.

Hi Dan, we're doing major merge/converting cleanup and we're triggering this scenario. I can confirm there is a race condition where if the converted Lead to Contact sync's to Marketo before the Converted (ghost) Lead does, then Marketo creates the new Contact as a new person, then later realises th...

This was so helpful. Thanks again Denise. I've updated my support ticket with this information and requested someone senior calls me to explain what multi-batch queue does on an instance, the pros and cons and what is required to have this feature disabled on our instance.Do you have any idea of any...

This sounds exactly like what happened!!!! Thanks so much for taking the time to respond. I'll look into it more.

This article (Understanding Merges in Marketo ) makes reference to the reason "Lead merge" which we added to our score programs which as far as I am aware, catches the manually performed lead merges . But it's unclear what causes the "leaddb" reason.

Grégoire Michel​ you might be my only hope to answer this?

I think that this is an edge case and for some unknown reason, Marketo has performed a Merge. There is literally one mention online of this "leaddb" merge reason here: How to identify leads manually merged in SFDC This is completely undocumented of course. I'll log a support ticket and struggle to f...

Can anyone explain this Merge IDs:1117921Merge Fields:Account Owner Email Address: sean.richards@alaress.com.auAccount Owner First Name: SeanAccount Owner Last Name: RichardsAccounts: 1Billing Country: AustraliaBilling Country Code: AUBilling State: QueenslandBilling State/Province Code: QLDGlobal R...