Syncing to Destinations
Send an Ours Privacy audience to an advertising 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. For downloading a file by hand instead, see Exporting a CSV.
Important: Advertising platforms are not HIPAA business associates and do not sign BAAs. Read Compliance for audiences before setting up a sync.
Before you start
- An Audience Destination configured in your account. Syncing works with Audience Destinations only, not with every destination connected to your account. Event destinations receive events, not membership, and are not offered here. Add one from Destinations first.
- An audience whose members have identifiers enabled for the destination. Each destination decides which identifiers it can use. Members without an enabled usable identifier are skipped.
- An Export Name on the audience. This is the label the platform displays, and it is required. 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. Press Generate for a neutral one. The card shows the exact form the destinations will see and lets you copy it, which is what you will search for in the platform's interface later.
- Read and accept the data-sharing terms shown in the card. They cover the four points on Compliance for audiences, and the confirmation you tick is a statement that you have the authority and a lawful basis to share this audience.
- Select the Audience Destinations you want the audience sent to. You can select more than one, and each gets its own independent sync.
- Save.
The audience then syncs daily, a little after midnight UTC. Nothing else to schedule and nothing to trigger.
If the card says you have no Audience Destinations yet, add one from Destinations and come back.
Destination readiness
Each destination in the card shows whether it can actually receive an audience today.
Available destinations sync normally.
Not available for sync covers destinations that receive events rather than membership.
Vibe CTV Audiences, MNTN Audiences, Facebook Custom Audiences, and Google Customer Match are available today.
What each run sends
Every destination receives the audience's Export Name and the identifiers you enable in that destination's settings. Identifiers are normalized and hashed with SHA-256 before they leave Ours Privacy.
The platform does not receive your audience conditions or internal audience name. Members with no usable enabled identifier are skipped.
Membership behavior depends on the destination. Vibe CTV Audiences and Facebook Custom Audiences replace full membership every run, so removals happen automatically. Google Customer Match refreshes members for one day at a time. MNTN Audiences adds or updates the members it receives, and does not automatically remove members who leave the audience.
A new audience appears after its first successful run, not the moment you attach it.
A sync sends the audience as you defined it, and does not filter on consent. Add a consent condition to the audience if one applies. See Compliance for audiences.
When a run is skipped
A sync is skipped rather than failed when the destination is Disabled, when the audience is not published, or when the destination has not been included in a published version of your destination settings yet. That last one catches people out: audience syncs read your published destination settings, so a destination you configured but never published is skipped. See Published Versions.
An empty membership is refused rather than sent. If every member lacks an enabled usable identifier, the run fails with that reason.
Reading the result
Ours Privacy records, for each run, how many members were delivered against how many were in the audience.
Those two numbers are the diagnostic that matters. A large gap means most of the audience had no enabled identifier to match on, and the fix is in your data collection, destination settings, or audience conditions rather than at the platform. See Previewing an audience.
What the numbers cannot tell you is how many people the platform recognized. A platform matches the hashed identifiers it receives only against people already in its own graph, so the audience there will be smaller than what you delivered, and a low match rate produces no error anywhere: the upload succeeds and the platform reports the audience as active. Check the platform's own interface for its match figure. See Audience Destinations.
Changing or stopping a sync
Add or remove destinations in the same card at any time. Removing one stops the audience being sent there; the list already on the platform stays until you delete it there.
Removing the last destination clears the acknowledgement. Turning the sync back on later means reading and accepting the data-sharing terms again, rather than inheriting a decision from months ago.
Renaming the Export Name changes the label the platform displays going forward, so if campaigns are already attached to the audience, you will be looking for a different name next time. Rename before attaching campaigns where you have the choice.
Deleting the audience should be preceded by stopping the sync, so it stops being sent before the definition disappears.
Practical notes
Review synced audiences on a schedule. A daily sync runs until somebody stops it. An audience built for a campaign that ended is still being sent every night.
One audience, several platforms. Attaching the same audience to more than one destination is normal, and each sync is independent. A platform that rejects one upload cannot hold up the others.
Platforms take their own time. After a sync lands, a platform may take up to a day or two to finish processing an audience update before it is usable for targeting. That is platform-side and is not something Ours Privacy reports on.
Search for the Export Name. When you go into the platform to attach the audience to a campaign, your internal name is not there. Copy the platform-facing name from the card.
Next Steps
- Audience Destinations for how the daily sync behaves and which platforms support it.
- Facebook Custom Audiences and Google Customer Match for destination setup.
- Compliance for audiences for the terms, naming, and applying consent.
- Targeting strategies for what to sync and why.
Need help? Contact support@oursprivacy.com.
How is this guide?