Previewing an Audience
Run a preview on an Ours Privacy audience to see an estimated member count and a sample of matching visitors, and learn what a preview does not tell you.
Use this page to check that an audience matches the people you meant before you export or sync it.
Running a preview
- Save your changes.
- Press Preview in the Audience Preview card.
- Read the estimated count and the sample.
- Adjust, save, and press Refresh Preview.
Preview does not create or send anything.
What you get
An estimated count. Treat it as the right order of magnitude. Is the audience roughly the size you expected, and is it big enough to be usable?
A sample of matching visitors with email, name, location, first and last seen, and consent. Do these look like the people you meant?
Read both. A plausible count with the wrong sample is the most common way a broken audience passes inspection.
Reading the result
Much larger than expected. Usually an event condition with no nested filter, so a page view condition is counting every page on your site. The next most common cause is an OR where you meant AND.
Much smaller than expected, or zero. Mismatched windows between conditions, a typo in an event name or URL fragment, too many ANDs, or a consent condition stricter than your data. Remove conditions one at a time to find the one responsible.
Right count, wrong sample. Look at what the rows have in common. It usually points at a missing condition rather than a wrong one.
Most rows have no email or phone. A sync can only deliver members who have an identifier the destination uses. Add a condition requiring one and preview again. That number is your realistic deliverable size.
What a preview does not tell you
- How many people the platform will match. Platforms match only against people they already recognize, so the audience there will be smaller.
- Whether the audience meets the platform's minimum. Meta's guidance for a customer list is at least 1,000 people, and Google recommends at least 5,000 for Customer Match.
The count you preview is the count a sync sends. Nothing is filtered on the way.
Next Steps
- Visitor conditions and Event conditions to adjust what you built.
- Exporting a CSV or Syncing to destinations once it looks right.
Need help? Contact support@oursprivacy.com.
How is this guide?