Syncing to Destinations
Send an Ours Privacy audience to an advertising or messaging platform every day. Set an Export Name, accept the data-sharing terms, select destinations, and read the delivered count.
Use this page to set up a daily audience sync, read the result, and stop one. To download a file instead, see Exporting a CSV.
Important: Advertising platforms are not HIPAA business associates. Read Compliance for audiences before setting up a sync.
Before you start
- An Audience Destination added and published from Destinations. Event destinations are not offered here.
- An audience whose members have the identifiers that destination uses. Members without one are skipped.
- An Export Name on the audience. See Export names.
Setting up the sync
Everything happens in the Sync to Destinations card on the audience.
- Set the Export Name if you have not already. The card shows the exact form the platform will display and lets you copy it.
- Read and accept the data-sharing terms.
- Select the destinations. Each one gets its own independent sync.
- Save, and publish the audience.
The audience then syncs once a day. There is nothing to schedule.
What each run sends
The Export Name and the identifiers enabled in the destination's settings. Advertising platforms receive them hashed; Mailchimp and Braze receive plain values because they match on the literal address or number. The platform never receives your conditions or internal name.
How membership changes land depends on the destination. Vibe and Meta replace the full list each run. Google refreshes it one day at a time. MNTN adds members but does not remove them. Mailchimp and Braze add and remove a tag or attribute value. See each destination's page.
A new audience appears on the platform after its first successful run.
When a run is skipped
A run is skipped when the destination is disabled, when the audience is not published, or when the destination has not been published yet. See Published Versions. A run with no deliverable members is refused rather than sent, so an audience is never cleared by accident.
Reading the result
Each run records how many members were delivered against how many were in the audience. A large gap means most members had no usable identifier, and the fix is in your data collection or your conditions.
What those numbers cannot tell you is how many people the platform recognized. A low match rate produces no error anywhere. Check the platform's own match figure.
Changing or stopping a sync
- Add or remove destinations in the same card. Removing one stops future sends; what is already on the platform stays until you remove it there.
- Removing the last destination clears the data-sharing acknowledgement, so turning the sync back on means accepting the terms again.
- Renaming the Export Name changes the label on the platform going forward. Rename before attaching campaigns where you can.
- Deleting the audience should come after stopping the sync.
Platforms can take a day or two to process an update before an audience is usable for targeting. A synced audience keeps running until someone stops it, so review them on a schedule.
Next Steps
- Audience Destinations for the platforms that can receive an audience.
- Compliance for audiences for the terms, naming, and consent.
- Targeting strategies for what to sync and why.
Need help? Contact support@oursprivacy.com.
How is this guide?