Saved audiences

Reuse the same devices, timing, throttling, visitor auth, seen notifications and URL rules across notifications, NPS and surveys.

An audience is a reusable targeting snapshot: devices, reach (throttling), timing delays, visitor auth, seen-notification rules, allow-list URLs and block-list URLs. You manage them under Settings → Audiences, then load them into a notification, NPS or survey targeting form.

Load copies into the form

Load copies audience rules into the targeting form only. Nothing is saved until you save the notification, survey or NPS settings. Editing the audience later does not change products that already loaded it — load again if you want the updated rules.

Create an audience

Open Settings → Audiences and choose New audience.
Name it clearly (for example “Pricing pages — desktop”).
Set devices, throttling, delays, visitor auth, seen notifications and URL allow / block lists — the same fields as on a Targeting tab.
Save. The list shows a summary of devices, reach, timing and URLs.

Load into a product

Open the Targeting tab on a notification, survey or NPS settings.
In Saved audience, pick an audience and click Load.
Review the copied fields, then save the notification / survey / NPS settings.

Shared targeting model

Notifications, NPS and surveys share the same targeting fields and URL rule format (including per-URL overrides, visitor auth and seen-notification rules). That is why one audience works across those products. Roadmaps and the status page do not use this targeting model. Host apps that need Logged in / Logged out targeting should call hubbo.identify().

URL patterns are documented in URL matching.