Manage Profiles Syncs

Profiles Sync list

From the Profiles Sync list page you can see all syncs in your workspace, along with:

• Destination — the BigQuery dataset and table the sync writes to.
• Last Sync — when the most recent run ran.
• Status — current state of the sync (Draft, Ready, Running, Complete, Error, Suspended).

Available actions

Edit

Click a sync to open the editor. You can change the name, filters, destination, and the selected keys and attributes.

Changes take effect on the next run. Because every run fully replaces the table, an updated set of columns is reflected in the table from the next sync onward.

Enable / Disable (Suspend)

Toggle the Enabled switch to start or pause scheduled syncing.

• Enabling a Draft or Suspended sync activates the daily sync schedule.
• Disabling a Ready sync pauses it. The table already written to BigQuery is left untouched — it stays as it was after the last run.

Run now

From a sync's detail page, use Run Sync to trigger an immediate run without waiting for the schedule. The sync must not be in Draft or Suspended state.

Duplicate

Clone a sync to use as a starting point for a new one. The copy is created in Draft status. Rename it, point it at a different destination table, and adjust the filters before enabling.

This is the safest way to test new keys, attributes, or filters without touching a live sync — especially since each sync fully replaces its destination table.

Delete

Deleting a sync stops all future runs and removes it permanently. The BigQuery table that was already written is not deleted — it remains in your dataset until you remove it yourself.

Use Suspend instead if you want to keep the configuration for future use.

Monitoring runs

Open a sync's detail page to see:

• Status — current state and the last sync date.
• Status message — details if the last run ended in Error.

For a complete history of every run across all syncs, audiences, and signals, use Sync History.

Handling errors

When a sync shows Error status:

1. Open the sync and read the status message.
2. Common causes:
   • The BigQuery connection's credentials have expired or lost access to the dataset — re-authenticate the connection and confirm its permissions.
   • The target dataset does not exist or the service account cannot write to it — see BigQuery Destination.
   • A key or attribute references a field that no longer exists in your warehouse — reselect the field.
3. Fix the underlying issue. The next scheduled run will retry automatically, or you can trigger Run Sync manually.