Audiences

Audiences let you describe a group of people using the data you already collect, see who matches, and then act on that group: download it as a CSV your ad platform accepts, or have Ours Privacy send its membership to an advertising platform every day. This is how retargeting and remarketing campaigns get built here. Conditions can describe who somebody is (consent, attribution, location, your own custom properties) and what they did on your site (pages viewed, forms submitted, events they never fired).

Audiences exist because the ordinary way to do this in healthcare marketing leaks. Exporting a spreadsheet called diabetes-nonconverters-q3 into Meta discloses a health condition to Meta in the file name alone, before anyone looks at a row. Ours Privacy keeps your descriptive name private, sends a separate meaningless name to the platform, and sends a hashed email as the only member attribute.

Open Audiences in app

Important: Advertising platforms are not HIPAA business associates. Meta, Google, and Vibe do not sign BAAs, and their terms prohibit uploading protected health information or consumer health data. Hashing an email does not make it anonymous: the platform matches the hash back to a person, which is the point of the upload. Read Compliance for audiences before you sync an audience anywhere.

---

Why use Ours Privacy Audiences

• The name you use internally never leaves. Every audience carries a private Name you write for your team and a separate Export Name that is the only label a platform or a CSV ever shows. See Export names.
• Behavior, not just attributes. Combine visitor properties with event conditions such as "viewed the appointment page at least twice in 30 days and never reached the confirmation page." See Event conditions.
• Check before you commit. Preview returns an estimated count and a sample of matching visitors, so a mistaken condition shows up before an upload does. See Previewing an audience.
• Two ways out, one definition. The same audience can be downloaded as a CSV formatted for Google Ads or Meta, or synced automatically to an Audience Destination. You do not maintain two definitions.
• Removals take care of themselves. Each sync sends the audience's full current membership and replaces the previous list, so anyone who stops matching drops out of the platform on the next run.
• What you preview is what you send. An audience is sent exactly as you defined it, with nothing filtered out on the way, so consent belongs in the conditions if it bears on who may be shared. See Compliance for audiences.

---

How it fits together

1. Create an audience and give it a private name plus an Export Name (use Generate if you would rather not invent one).
2. Add conditions in Visitor Properties, Event Behavior, or both. An audience needs at least one condition before it can do anything.
3. Preview to see the estimated size and a sample of who matches, then adjust the conditions until the group looks right.
4. Activate it: download a CSV in the format your platform expects, or select Audience Destinations and let Ours Privacy send membership daily.

---

Key pages

• Audience concepts: what an audience is, what published means, and the difference between exporting and syncing.
• Building an audience: the walkthrough, from creating one to activating it.
• Visitor conditions: the properties you can filter on and every operator available.
• Event conditions: counts, rolling time windows, event property filters, and the never-did-this pattern.
• Previewing an audience: how to read the estimate and the sample, and what a preview does not tell you.
• Export names: the second name, why it exists, how to generate one, and how to change it safely.
• Compliance for audiences: the data-sharing terms, naming, applying consent, what platforms receive, and what stays with you.
• Exporting a CSV: the three export formats, what gets hashed, and the matched-row count.
• Syncing to destinations: set up a daily sync, read a sync result, and stop one.
• Audience Destinations: which platforms can receive an audience and how the daily sync behaves.
• Targeting strategies: exclusion audiences, retargeting, lookalike seeds, and layering them.
• Recipes: worked audience configurations you can copy, grouped by goal.
• Audience FAQs: sizing, match rates, timing, consent, naming, and access questions.

---

Works with the rest of the platform

• Cookie Consent: consent categories become conditions, so an audience can require an accepted advertising category rather than only excluding rejections.
• Web Analytics: every event you already collect is available as an event condition, with no extra instrumentation.
• Experimentation: build an audience of the visitors who saw one variant, using From experiment in the Event Behavior section.
• Audience Performance: measure how an audience-shaped group converts and what revenue it drove.
• Short Links: target visitors who scanned a QR code or arrived through a specific link or campaign.
• Destinations: event destinations receive events; Audience Destinations receive membership. Most accounts use both.

---

Availability

Audiences are available to all accounts, subject to a per-account audience limit. If you have reached your limit and need more audiences, contact your account representative. Creating, editing, previewing, and exporting are each governed by their own permission, so ask your account administrator if an action is disabled for you.

Audiences are built and activated in the dashboard. There is no SDK to install, and building an audience does not require any instrumentation beyond the events and visitor properties you already collect. Audience membership is not exposed through the Platform API today, though the audience conversion report is available there.

---

Need help?

Reach out to support@oursprivacy.com with any questions about audiences.