It sounds like you need to do some cleanup in your Matketo instance.
@gailhjohnstone wrote:
Hi @Darshil_Shah1 ,
Thanks for the reply. We have had speed issues on-going for a long time now, but recently we had an issue that stopped the campaign synced. This has now fixed, but I worried about the backlog as I can see contacts that became campaign members a month ago that still haven't been added as members to the SF campaigns.
- Looking at the sync status, which operation is responsible for pushing campaign members from Marketo programs into Salesforce campaigns via the native program sync? I can see pull, but no push under the campaign member object? What am I looking for here to understand whether program members are being passed into Salesforce campaigns?
Well, pull update activity is def not the one that's pushing updates from Marketo! Since you're seeing campaign data from Salesforce syncing to Marketo- it'd be worth checking whether the Sync user has the apt rights to make updates on the Campaign-related objects (Campaign, Campaign Member, and Campaign Member Status).
We have too many fields (over 800) on the lead object that are synced with SF. Could this be a likely cause of the campaign sync speed issue?
Well, the native sync prioritizes syncing lead/contact data over the campaign-related data, so if you have a lot of data (in the form of field data/number of lead/contact records) to sync back and forth, you'd likely see sync delays in the objects that come after the lead/contact objects in the sync-priority order (e.g., Campaign object). You should consider hiding the fields that you no longer use/need.
We also have many marketeers using the flow step 'sync to SF campaign' rather than the native program sync. Would this impact the campaign sync speed?
Well, the Sync to Salesforce Campaign flow step is an alternative way to keep the members in the Marketo program and Salesforce Campaign in Sync. Both methods, i.e., the native program-campaign sync and manual sync via flow steps have their own pros and cons, but using one or the other should not cause backlogs. In a perfect world, updates via both should sync in near real-time over to the Salesforce.
Also, as a best practice, you should consider sticking to one or the other method for keeping your program and campaign members in sync instead of using one for a few programs and the other method for the rest.
Do you see similar sync delays while syncing members using the Add to Salesforce Campaign flow step?
- Finally, what impact does the API capacity on the Salesforce end have? Would increasing the capacity help, and is this possible?
Well, syncing data over to Salesforce from Marketo via the native connector doesn't use the API from the quota you have for your custom integrations/API calls (in the Admin > Webservices).
To give you an idea, during a single sync session, Marketo makes 25 API calls to check if your Salesforce objects need updating. Because your Salesforce sync happens in 5-minute intervals (default setting), each day Marketo makes 7200 API calls to your account to see if any updates are needed.
There's some system-level throttling used so the integration doesn't make a ton of API calls to sync the data back-and-froth, and Salesforce determines your API call limit based on the edition and licenses you have. For many Salesforce users, particularly Enterprise Edition users, the number of API calls made by Marketo is usually not a problem. Check out this knowledgebase article on How Marketo Uses the Salesforce API.
.png)