This post it to elaborate some strategies to handle the "sync with Marketo", based on the findings we had on how this field really work ("Sync with Marketo" mysteries part 1)
Just set the "Sync with Marketo" to False in SFDC before enabling the sync. In the initial sync process, stop at the field mapping step, ask Support to enable the filter and, when it's done, complete the sync.
This may be needed for a progressive roll out in large orgs.
Start with disabling ("Sync with Marketo" = False) for everything in SFDC and progressively set the "Sync with Marketo" field to True for the BU's or geographies you want to activate.
From our findings, the first way you should consider to set this up is to stop the sync FROM Marketo. Unchecking the "sync with Marketo" will propagate to SFDC at next sync, and from there, the sync will stop. So the smart campaign to set up to do this is:
The "sync with SFDC" flow step is not mandatory, you may just rely on the automatic sync to happen. Still, having this step in the flow enables to make sure that the sync has occurred before deleting the lead. If you do not use a "Sync to SFDC" step, insert a "wait 1 hour" instead.
If for various reasons, you do not want to use Marketo to stop the sync but you want to do it in SFDC, then use a time based workflow so that the "sync" field is not unchecked immediately. This will leave time for the other value changes to be propagated to Marketo, where you will be able to use these value changes to ultimately delete the lead, after another wait of 2 hours.
|Lead/contact values are edited and trigger a Time based workflow for 1 hour
|On sync, the values are also changed in Marketo to reflect the changes from SFDC. Trigger a smart campaign to delete the lead, but start by waiting 2 hours
|End of the TBW. The "sync to Marketo" field is set to False
|The sync stops
|The sync stops.
|End of the wait, the lead is deleted
You do not have a choice here: the only place you can do this is in SFDC, even if you have not deleted it yet from Marketo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.