How to Target the Right Audience on Privy

Privy display targeting combines audience eligibility, a trigger, appearance limits and a schedule. A visitor matching the audience is only one part of the configuration. Start with a written description of who should see the offer, then translate it into rules in the display’s Settings.

The workflow and platform availability below come from Privy’s audience and settings guide, checked September 6, 2026. The test examples are editorial exercises, not measured customer results.

Set the campaign in four passes

1. Audience: choose the conditions identifying the intended visitors.
2. Trigger: select time, scroll or exit intent. With multiple triggers, the first matching event opens the display. With none, use a tab for manual opening.
3. Appearance: choose the repeat-display limit. Privy documents a one-day default; removing the limit permits repeated triggering within a session.
4. Schedule: select ongoing availability or a date range, then review the campaign before launch.

Avoid changing every setting while troubleshooting. Save the original configuration and test one suspected cause at a time on a controlled page.

Choose rules that match available data

Check the connected platform and actual field values before assuming a missing condition is a plan restriction. The source documents these platform dependencies; it does not establish that every missing-rule problem has the same cause.

Make Match All and Match Any explicit

Match All requires every condition. Match Any accepts at least one. For a hypothetical campaign targeting mobile visitors on a particular page, the difference is:

These results describe audience eligibility only; triggers, schedules and appearance limits still need checking. Use this table as a test brief before publishing. If your intended audience is an intersection, Match Any can broaden it beyond what you meant.

Test both a match and an exclusion

Record the campaign, device, URL, visitor history and expected outcome for each test. Verify at least one eligible visitor and one visitor who fails a condition. For cart rules, test below and above your chosen threshold and confirm the boundary behavior matches the operator selected in your account.

If nothing appears, inspect installation, publication and scheduling before rewriting the audience. Then inspect the trigger and appearance history. A fresh session is useful for isolating history, but it does not prove a returning visitor will behave identically.

If the wrong people see the offer, check Match Any versus Match All, current versus initial URL, and session versus all-time history. Privy defines a session as ending after 30 minutes of inactivity. Do not mistake a new pageview for a new session.

Separate visibility from signup permission

Privy’s advanced signup rules can restrict repeat signups or accept new contacts only. A visitor may therefore see a display but be unable to submit an address. Test the error state as well as successful submission, and explain the restriction in the offer where appropriate.

For manual opening, follow the clickable-tab guide. To inspect data collected at signup, use the Profile Attributes guide.