Event Conditions
Filter an Ours Privacy audience on behavior: event counts inside a rolling window, filters on the event's own properties, and the zero-count pattern for excluding converters.
Use this page as the reference for the Event Behavior section of an audience. For attributes rather than behavior, see Visitor conditions.
What an event condition says
Every event condition answers one question: did this visitor perform this event this many times in the last this many days?
- The event, picked from the ones your account collects.
- The count: an operator and a number, such as at least 2 or exactly 0.
- The window: a number of days, counted back from now.
Optionally, nested conditions narrow which occurrences count.

Counts
The count operators are the usual comparisons: exactly, at least, at most, more than, fewer than. At least 1 is how you include people who did something. Exactly 0 is how you exclude people who did.
Windows
The window rolls, so a 30-day window today covers a different 30 days than it did last week.
| Window | Fits |
|---|---|
| 3 to 7 days | Retargeting while your brand is still top of mind |
| 14 days | A campaign flight |
| 30 days | The default for most audiences |
| 90 days | Long consideration cycles, or audiences otherwise too small |
A longer window makes an audience bigger but less current. When two conditions describe the same funnel, give them the same window.
Filtering which occurrences count
A bare event condition counts every occurrence. For page views that is almost never what you want, because every page fires one. Add a nested condition such as page URL contains /appointments so that only those occurrences count.
You can nest on anything the event carries: the page URL, the UTM values in effect, and any properties you attach. Every operator from Visitor conditions works here.
Rule of thumb: an event that fires on many pages needs a nested URL condition. An event that is specific by nature, such as a form submission, usually does not.
The zero-count pattern
A count of exactly 0 means the visitor never performed the event in the window. Almost every effective retargeting audience is two conditions:
- At least one occurrence of an interest signal, such as a view of a service page.
- Exactly zero occurrences of the conversion, such as a view of the confirmation page.
Without the second condition you pay to advertise to people who already converted. Pick the last step that only completers reach as the conversion: a confirmation page rather than the first step of a form. See Targeting strategies.
Combining event conditions
AND is the normal choice and is what funnel-shaped audiences are made of: did this, did not do that. OR is for several events that count as the same signal, such as any of three form submissions.
Audiences from an experiment
To target the visitors who saw a specific variant, use From experiment in the Event Behavior card. It fills in the impression event and variant filter for you. See Experimentation.
Next Steps
- Previewing an audience to validate what you built.
- Recipes for worked event configurations.
- Targeting strategies for exclusions, retargeting, and lookalike seeds.
Need help? Contact support@oursprivacy.com.
How is this guide?

