What causes sync backlogs

Whether the update is made on the Marketo Engage side or the CRM side, it will trigger the record to be resynced to update the information on the other end through the regular Marketo Engage to CRM sync cycle. Whenever an update is made to a record on Salesforce, it generates a System Modification Time Stamp, referred to as ‘SysModStamp.’ This queues a change to sync.

When a large amount of updates are made (like from a field value changing), many records are altered, causing new SysModStamps. A large number of person record updates then need to be resynced between Marketo Engage and your CRM, sometimes creating a momentary backlog.

Best practices for managing sync backlogs

Fields visible to Sync User: Ensure that the fields visible to sync are only those that need to be synced and have value to marketing efforts. Any update to a record in Salesforce that updates the last modified timestamp will queue a record to the sync backlog, and unnecessary fields syncing may slow more important fields under sync. If the unnecessary fields are hidden from the sync user, updates to those fields will result in a skip which is much quicker than an update. Work with your Salesforce Admin to review best practices here and update which fields are visible to the Marketo Sync User.

Hide or filter unnecessary records: If a record is not marketable, it may be wasting sync resources. If the sync user cannot see it, then it won’t waste resources trying to sync it. Marketo Engage Support can assist setting up a sync filter to inhibit records from syncing based on additional criteria. More information about setting up a Custom Sync Filter can be found here. It is strongly recommended to use index fields within Salesforce (contact salesforce for further information).

Schedule bulk updates during non-critical hours: Review your data sync patterns to identify non-critical periods. Review if bulk updates can be scheduled in these non-critical periods if possible.

Frequently Updated fields: Some fields are prone to frequent updates. For example, currency fields that are subject to currency changes. Review if these need to be synced, or if the fields should be designed differently. If you have other fields that are updated frequently and are not needed, hide them from the sync user. Be sure to discuss with your SFDC admin integrations that might be updating fields.

Custom objects: Periodically review custom objects enabled to sync and disable those that no longer need to be synced.

Activities: Review if any activities enabled sync that may be removed from sync. These activities only sync once per day per lead.

Review Sync errors: Exception handling may slow down the sync. Reviewing user notifications and resolving errors can improve sync health.

Contact Support: If you’re following all of the above best practices and are still experiencing significant backlogs, contact Marketo Engage Support.

Previous pageLog in Using OAuth 2.0
Next pageSalesforce Sync Errors

Marketo Engage