Re: Marketo and Salesforce CRM sync

Deeps · ‎12-12-2022

Hi Team,

Please assist with this question below:

1. What's the best practice to sync Marketo and salesforce

- At the program level - if yes, why?

or

2. Establish the sync between Marketo and Salesforce at the program level and disconnect it -

- Add the 'change status in SFDC' in the flow step to push back the program statuses in SFDC

Thanks,

Deepthi.

Darshil_Shah1 · ‎12-12-2022

Well, this really depends on how your instance and SFDC org are set up and what are your use cases -

1. The channel progression status values and SFDC campaign status values must match exactly (1-1) with each other for you to use the OOTB Marketo-Campaign sync. If the status values don't match, you'd need to rely on the "Change Status in SFDC "flow step in Marketo for updating the SFDC campaign status.

2. If there are any records that you do not wish to create/sync in SFDC, then the OOTB Marketo program-SFDC campaign sync should not be used as it'd create/update all the program members over to SFDC.

3. Lastly, program-campaign sync allows you to sync only one Marketo program with a salesforce campaign, if you have multiple programs that need to be synced with a single SFDC campaign, then you should not use the OOTB program-campaign sync.

Vinay_Kumar · ‎12-12-2022

Well, I would suggest going with Add to SFDC or Change Status in SFDC flow steps as this will only sync the qualified leads to the salesforce campaign. And if you use program-level sync then this will sync all the program members to salesforce.

SanfordWhiteman · ‎12-12-2022

There is no single correct answer to this question!

Answers vary not just across Marketo instances, but within the same instance. Different business and tech requirements mean different approaches. Sometimes, the automatic Marketo Program-SFDC Sync is unmistakably better. Other times, the flow step is the only way.

As Darshil pointed out, there are some things one feature can do that the other can't. Performance (batch sync) and timeliness (immediate sync) are additional considerations.