Understanding Syncs in Chord

introduction syncs power audience activation in chord when you send an audience to a destination, such as an esp or ad platform, you create a sync this page explains how syncs work and how to manage them what is a sync? a sync connects a chord audience a destination a defined set of mapped fields it controls how data moves from chord to your external platform a sync does not change your underlying audience logic it only controls how that audience is delivered what you configure in a sync when setting up a sync, you define 1\ destination where the audience is sent 2\ field mappings how chord fields match destination fields clear mapping ensures the destination platform receives data in the correct structure 3\ sync behavior depending on the destination, you may configure full refresh vs incremental updates list additions or removals record update behavior viewing sync history each sync includes a history of past runs you can review last run details source details destination details full sync history if a sync fails, start by reviewing the error details in the run history most issues relate to missing required fields invalid mappings destination side validation rules editing a sync to edit a sync navigate to data activations click on manage syncs select the specific sync you wish to edit click on the three veritcal dots icon in the actions column click edit sync you can also manage syncs via the audience destinations tab on the audiences page all settings are available in one structured modal changes apply to future runs historical runs remain unchanged deleting a sync deleting a sync stops future data updates does not delete historical records in the destination platform does not delete the underlying audience to delete a sync navigate to data activations click on manage syncs select the specific sync you wish to delete click on the three veritcal dots icon in the actions column click delete sync you can also delete syncs via the audience destinations tab on the audiences page best practices confirm required destination fields before mapping review sync history after your first run keep field naming consistent across platforms test new syncs before launching time sensitive campaigns