Audience Destinations
Audience Destinations send the members of an Audience Builder audience to an advertising platform on a daily schedule, using hashed identifiers rather than raw email addresses.
An Audience Destination receives the membership of an audience rather than a stream of events. You build the audience once in the Audience Builder, pick which Audience Destinations it syncs to, and Ours Privacy sends the matching people to that platform daily so you can target them in your campaigns.
Because these destinations receive people and not events, they have no allowed events and no event mappings. A single settings page holds the credentials, and the audience itself decides who gets sent.
Why use an Audience Destination
- No manual CSV round trip. The audience is rebuilt and re-sent daily, so your targeting keeps up with your data instead of aging from the moment you exported it.
- You control how the data is served. Your criteria decide who is included, and the Export Name is the only label that travels with them. Email is the only member attribute sent, hashed in the form the receiving platform specifies rather than as a raw address.
- Removals happen on their own. Each run sends the audience's full current membership and replaces the previous list, so anyone who no longer matches your criteria drops out of the platform audience.
- One audience, several platforms. Attach the same audience to more than one Audience Destination and each gets its own independent sync.
- Nothing to schedule. There is no job to configure or trigger. Selecting the destination on the audience is the whole setup.
Available Audience Destinations
Vibe CTV Audiences is the one Audience Destination that syncs today. It sends audiences to Vibe for connected-TV targeting.
Other platforms appear in the destinations list and accept credentials, but cannot sync yet. An audience attached to one of them does not deliver, and the attempt is recorded against the audience as failed rather than silently doing nothing:
If a destination is listed in the app but has no page here, treat it as not yet syncing and check with your account representative before planning campaigns around it.
How syncing works
- Once a day, Ours Privacy re-evaluates every published audience that has at least one Audience Destination selected, so each run reflects who matches today rather than who matched when you created the audience.
- Each audience and destination pair syncs on its own, so a platform that rejects one upload cannot hold up the others.
- Each member's email address is hashed in the form the platform specifies, duplicates are collapsed, and members with no usable email address are skipped.
- The membership is uploaded to the platform, replacing the audience there.
A run is skipped when the destination is Disabled, or when the destination has not been included in a published version yet. Because every run sends the full membership, a skipped or failed run corrects itself on the next one: there is no backlog to catch up on.
What the platform receives
Two things: the audience's Export Name, and one hashed email address per member. Your internal audience name, your filter criteria, and every other visitor attribute stay in Ours Privacy. Names, phone numbers, and addresses are not part of an audience sync at all.
Email is the only identifier an Audience Destination matches on. Each address is hashed with SHA-256 before upload, in the form the receiving platform specifies, and members whose record has no usable email address are skipped rather than uploaded. Platforms differ in how they want an address normalized before hashing, so the specifics live on each destination's page.
The Export Name is the one label that reaches the platform, and the platform displays it in its own interface. Ours Privacy blocks Export Names that carry health context for that reason, and sends a simplified form of the name (lowercase and hyphenated). See Export names for how to set it.
Important: Advertising platforms are not HIPAA business associates and their terms typically prohibit uploading protected health information or consumer health data. Hashing an email does not make it anonymous: matching the hash back to a person is what the upload is for. Ours Privacy asks you to accept data-sharing terms covering this before an audience can sync. See Compliance for audiences.
Match rates and minimums
A platform can only match a hashed email against a person it already recognizes, so expect the platform-side audience to be smaller than the count in Ours Privacy.
A low match rate is not an error anywhere. The upload succeeds, the platform reports the audience as active, and it simply matches fewer people than you expected. Nothing fails, so nothing tells you. Two numbers are worth checking whenever a synced audience underperforms:
- How many members had an email address to match on. Ours Privacy records the delivered count against the audience total for every sync, which makes it obvious when most of an audience had nothing to match on. If the two numbers are far apart, the fix is in your data collection or your audience criteria, not on the platform side.
- The platform's own minimum before a list is usable for targeting. Meta and Google each publish one, and a list below it can look healthy while never becoming targetable. The individual destination pages cover the current figures and where the platform reports your match rate.
If the delivered count looks healthy but the platform reports few or no matches, contact support@oursprivacy.com with the audience and the destination.
Next Steps
- Syncing to destinations to set up a sync on an audience.
- Vibe CTV Audiences for the setup walkthrough of the destination available today.
- Compliance for audiences for the terms and the advertising consent gate.
- Destination Overview for how destinations work across the platform.
Need help? Contact support@oursprivacy.com.
How is this guide?