Use this section to tune the rate and resource utilisation of bulk syncs according to the volume of data you need to sync and the capacity of your system. We have set some default configurations that balance speed and efficiency.

Bulk contact (Customer, Guest, Subscriber) and insight data syncs (Order, Catalog) run continuously. When the relevant cron job runs, the sync will process all available rows in batches and stop only when everything has been synced.

Example: Syncing 100,000 customers with the default configuration:

Tips:

Continuous sync means a continual cycle of:

A mega batch is, by default, the result of multiple database queries.

Setting a break value is a way to limit the work done in any single cron 'sync' execution. By default, it is not set to expedite fast data transfer. If you are concerned about resource utilisation, use the break value to sync data in manageable chunks.

If the break value is set, continuous sync will stop when the total number of processed rows exceeds this. The sync then finishes and waits for the next cron run to process more rows. Setting break value applies to all continuous syncs; it effectively makes them non-continuous.

Example: Syncing 100,000 customers with break value set to 20,000:

Overloaded server due to long-running cron processes

Set the Transactional data break to address this issue. Although the sync rate will slow down, it allows for monitoring without the concern of runaway processes.

Impact of Excessive Database Queries on the System

To mitigate this, reduce the Contact sync batch size to limit the number of customers being exported data for in any one loop. Unmap the most query-hungry data fields in Dotdigital > Data Mapping, starting with:

Cron Tasks Stuck in running for an extended time:

Dotdigital sync crons showing as 'missed'

This is also expected behavior. A cron process may over-run its scheduled window if it is processing large amounts of un-processed or not-imported data. Magento's cron scheduler will only spawn one running job of each type at a time and will mark subsequent jobs as 'Missed' until the running job is finished.

Imports failing due to unserialized errors or bad JSON data

This issue likely occurs when the sync attempts to save too much data into the import_data column fails. To resolve this, adjust the relevant mega batch size. This problem should occur less frequently after v4.27.0.

If you do not want to manually map the key information that you store on customers from your website to Dotdigital contact data fields, then you can use this option to do it automatically.

To automatically map your data fields:

If you want to synchronise your store with a different Dotdigital account, or even synchronise a different store front to a new Dotdigital account. To ensure this works correctly you need to delete all the customer contact IDs that have been stored against the customers, as these are unique to the Dotdigital account.

To delete all contact IDs:

Instead of waiting for the next automatic contact data synchronisation in your account, you can manually run one instead.

To run a manual sync:

You can refresh all of the customer data stored in Dotdigital that you've already imported from your store, marking it all for import again and ensuring it's up to date.

To reset your customer data:

Use this setting to set the batch size of contacts you want to sync to your Dotdigital account with each data import:

Use this setting to set the batch size of transactional data you want to sync to your Dotdigital account with each data import:

This setting can be enabled to sync subscribers’ sales data to Dotdigital.

Enabling this setting increases server load and overall sync times.

This setting can be enabled to remove the /pub directory from image URLs in catalog sync and insight data:

When you install the Dotdigital for Adobe Commerce connector, we generate a unique passcode that is used to access external dynamic content. By using this passcode you can be sure that basket contents and coupon codes can be viewed only if that passcode is sent with the GET request to the external dynamic content URL, adding security.

Learn more in Edit your dynamic content security settings in Magento Open Source and Adobe Commerce.

You can also enter a list of requesting IP addresses that these URLs will display for when requested from them:

Set how frequently you want cron jobs to run:

System alerts can notify you when certain functions go wrong in your account.

When enabled, this setting allows you to send in-app system messages to admin users when errors that may affect the Dotdigital extension are detected:

When enabled, this setting allows you to send system alert email notifications when errors that may affect the Dotdigital extension are detected:

Use this setting to specify if you use a PWA storefront URL that is different from your account’s default frontend base URL: