Visitor Conditions
Filter an Ours Privacy audience on visitor attributes: consent categories, first-touch attribution, location, click IDs, and your own custom properties.
Use this page as the reference for the Visitor Properties section of an audience. For behavior rather than attributes, see Event conditions.
What you can filter on
The property list reflects what your account collects. These groups are always present.
Consent. Accepted Consent Categories and Rejected Consent Categories. Each holds a list, so use contains. To require affirmative opt-in, use Accepted Consent Categories contains advertising. To exclude recorded rejections, use Rejected Consent Categories does not contain advertising. The first is stricter: someone who was never asked is not a rejection. See Cookie Consent.
Attribution. First-touch and current-session UTM values, referrer, and referring domain, plus click IDs from ad platforms. First-touch properties are prefixed with initial and are usually the ones you want, because they describe how the person originally found you.
Identity and profile. Email, phone, name, date of birth, gender, external ID, company, and job title, where you collect them. Requiring Email is not null is a useful habit for any audience you plan to sync, because it shows the deliverable size in Preview.
Location. City, state, country, ZIP code, and time zone.
Timing. First seen and last seen, for "active since" and "has not been back since" audiences.
Custom properties. Anything you send on the visitor. New properties appear once Ours Privacy has seen them. An advanced entry mode lets you type a property path directly.
Operators
Every operator is available on visitor conditions and on the nested conditions inside an event condition. The dropdown describes each one; these are the ones you will use most.
| Operator | Use it for |
|---|---|
| is / is not | An exact value. Case-sensitive |
| contains / does not contain | A substring, or an item in a list such as consent categories |
| starts with / ends with | The beginning or end of a value, such as a URL path |
| is found in / is not found in | A comma-separated set of values, such as CA, OR, WA |
| is null / is not null | Whether the property has a value |
| is true / is false | Boolean properties |
| greater than, less than, and so on | Numeric comparison |
| is before / is after / is between | Dates. is between takes two dates separated by a comma |
| matches regex | Several URL shapes in one condition, with an ignore-case variant |
Combining conditions
AND narrows: every condition must match. OR broadens: any one can match, which is useful for spelling and casing variants of the same thing.
When both the Visitor Properties and Event Behavior sections have conditions, a visitor has to satisfy both.
Next Steps
- Event conditions to filter on behavior.
- Previewing an audience to check what your conditions match.
- Recipes for configurations that combine both condition types.
Need help? Contact support@oursprivacy.com.
How is this guide?