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 values.
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 what identifiers are sent. Your criteria decide who is included, and each destination's settings decide which identifiers it can receive. Enabled identifiers are hashed in the form the receiving platform specifies rather than sent as raw values.
- Membership behavior is destination-specific. Vibe and Meta replace their full membership every run. Google refreshes a one-day membership window. MNTN adds or updates members it receives, so removals need to happen in MNTN.
- 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, MNTN Audiences, Facebook Custom Audiences, and Google Customer Match sync today.
If a destination is listed in the app but has no page here, 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 enabled identifiers are hashed in the form the platform specifies, duplicates are collapsed, and members with no usable identifier are skipped.
- The destination updates the platform audience according to its membership model. Check the destination page for removal behavior.
A run is skipped when the destination is Disabled, or when the destination has not been included in a published version yet.
What the platform receives
The audience's Export Name and the enabled, hashed identifiers. Your internal audience name and filter criteria stay in Ours Privacy.
Each identifier is hashed with SHA-256 before upload in the form the receiving platform specifies. Platforms differ in which identifiers they accept and how they normalize them, 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, so keep it meaningless. A simplified form of the name is sent (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. Ours Privacy asks you to accept data-sharing terms before an audience can sync. See Compliance for audiences.
Match rates and minimums
A platform can only match a hashed identifier 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 enabled usable identifier. 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 and MNTN Audiences for destination setup.
- Compliance for audiences for the terms, naming, and applying consent.
- Destination Overview for how destinations work across the platform.
Need help? Contact support@oursprivacy.com.
How is this guide?