Aaron_Dear

Response:Thank you for letting me know. Let me explain this in detail.All the Sync between Marketo and SFDC happens through global sync, except for the sync that is performed manually.When a record is skipped from syncing between Marketo to SFDC, due to validation errors, the same record will not ge...

Hah, literally the same issue here!

Story of my life. GTW is infamous for 403 errors. A launchpoint re-auth is all it takes to "fix" it until a week later.

Hey Amanda! Answers below:Did the leads exist in SFDC before being associated to the program/event? Nope. They were sourced from a form fill out in Marketo.I have come across the scenario that if sync fails on the first attempt (the attempt to create a lead in SFDC), it won't try again, and you have...

Support person's quotation:I would once again like to refer you to another article I found about this subject. It is actually written by one of our TSEs.The ruleset for which record is considered to be the winner, actually depends on the activity being performed, and this article goes over a lot of ...

Agreed. In our instance, we have tested using the API to surface Marketo activities into our CRM. While it works, the potential of ID swapping concerns me. We might just need some logic to refresh IDs every so often.Here's the exact response I got from support:Sorry for the misunderstanding, a lead ...

I am led to believe there is a pool of available IDs from previously deleted leads that "frees up" after a certain period of time. As for confirmation:I noticed it myself a while ago. I had 3 leads, with the older 2 (both in SFDC and Marketo age) having a high ID (6 figs), and the newer one having a...

Been doing some testing around this - my support guy pointed me here.To clarify, email sends will go to Marketo's smallest ID. That is NOT always the one created earlier.After a lead record has been deleted from database, Marketo will eventually start associating newer IDs to older records. For exam...

Ah, excellent. So I could absolutely do this then. Thanks Sanford!