Sync Configuration Refresh Feature

What it does

When you change a sync's settings, those changes normally reach new visitors right away, but returning visitors can keep using the older settings until their cached configuration naturally expires.

Auto-resync closes that gap. When you turn it on for a specific sync, any returning visitor will re-fire that sync with the latest settings on their very next page load after you deploy the change.

The setting is per sync and off by default, so you can enable it just for the syncs where keeping returning visitors current matters most. A few limits worth noting:

• Only syncs that are on will re-fire. If a sync is off, it doesn’t work
• It doesn't apply to past changes. A returning visitor picks up a change only if they come back after you deploy it.

Steps

1. Open the Analytics Builder
2. Choose how your file is hosted (self-hosted or MetaRouter cluster)
3. Go to the sync you want
4. On that sync's card, check Auto-resync [Sync Name] on settings change
5. Save your changes. The setting only takes effect once saved.
6. Rebuild and deploy the updated AJS file:

• Self-hosted: download and deploy the file to your environment.
• MetaRouter cluster: upload the file to your cluster.

The change takes effect for returning visitors on their next page load after deployment.

Auto-resync only re-fires a sync when something about that sync's configuration actually changed, for example, a change to a configuration field, its consent category, or its TCF setting. Rebuilding with no changes, or simply toggling the checkbox, does not count as a settings change.