Audiences

Audiences and Datasets are the suppression and allow-list system for Ping Control. You create them on the Audiences page, then assign them to individual relay entities (Publishers, Campaigns, Buyers, Targets) in each entity's Relay settings.

• An Audience is a named rule set that controls which pings are suppressed or allowed based on which entities they come from.

• A Dataset is a collected list of phone numbers or ZIP codes. Datasets are the data source that Audiences draw from.

The Audiences page

The Audiences page (/home/relay/audiences) has two tabs: Audiences and Datasets.

Audiences tab

The Audiences table shows all audiences in your org with the following columns:

Click New audience to open the creation form. Click any row to open the audience detail panel on the right.

Audience detail panel

Settings block: set the audience name. Saves on blur.

Datasets block: link one or more Datasets to this audience. Use the Select button to pick datasets. Click a linked dataset name to open the dataset panel inline. Remove with the X button.

Ping Control traffic block: controls whether this audience actively filters pings.

• Enable / Disable toggle — requires a confirm dialog. When disabled, the audience exists but has no effect on traffic.

• Traffic scope — configure which entities trigger suppression or allow-list behavior. Two modes:

  Local mode — entity-level rules. Add Publishers, Campaigns, Buyers, or Targets using the selector buttons. For each entity added, set the operator to Allow or Deny.

  Global mode — a single operator applies to your entire org. A warning appears: "Globally applied filter will affect every ping on Organization level." and ""Allow" will suppress everything except matching items."Switching to Global sets the operator to Deny by default.

Exports block: placeholder for future Meta and Google export integrations. All buttons are disabled; shows "Coming soon."

Delete: available from the action menu (ellipsis). Requires confirmation: "This will permanently delete the audience and all its exports."

Datasets tab

The Datasets table shows all datasets with these columns:

Click New dataset to open a type selection:

Type cannot be changed after creation.

Dataset detail panel

Settings block: name field, saves on blur.

Limits block (Anti-spam list only): configure the abuse detection thresholds.

• Daily limit — how many pings from one phone number per 24 hours before suppression triggers (minimum 5).

• Weekly limit — same for a 7-day window.

• Block for — how long the number stays suppressed after hitting the limit. Options: 1 year / 6 months / 1 month / 1 week / 3 days / 1 day.

Both daily and weekly thresholds are independent — triggering either one starts the suppression timer.

Data sources block (Phone list and ZIP list only): defines where the dataset collects entries from.

• Sources use OR logic — a phone or ZIP is collected if it matches any source.

• Add sources by Publisher, Campaign, Buyer, or Target.

• Each source has a condition dropdown: "Only calls" / "Only pings" / "Pings and calls." For ZIP lists, the condition is always "Only calls" (locked). For non-Experimenter users, the condition dropdown is also locked.

• Remove all clears all configured sources.

• No sources state: shows "All network · Only calls" — the dataset collects from all traffic.

Collection rules block (Phone list and ZIP list only): additional filters that a phone or ZIP must satisfy to be collected.

• Rules use AND logic — a phone or ZIP is only collected when it satisfies all rules.

• Add rules via the Rule dropdown:

  • Detector — select a score question; set the required output (YES/NO for binary questions, specific value for others).

  • Attribute — filter by caller profile attributes (age, income, state, etc.). Requires profileEnrichment org setting or Experimenter role; otherwise shows "Attribute · coming soon."

• Remove all clears all rules.

Ping Control traffic block: same Enable/Disable toggle and Traffic scope as the Audience panel, but with one addition — a header note: "Direct rules apply to traffic matched by this dataset, independent of audiences." A Remove allbutton (trash icon) clears all entity rules at once.

Audiences block: link this dataset to one or more Audiences. Selected audiences shown as removable tags.

Captured entries block (Phone list and ZIP list only): shows all collected phone numbers or ZIP codes.

Columns: Value · Added · Last seen as · Remaining (TTL countdown: "Nd HH:MM", or "Allowed" if the entry has expired)

Row checkboxes + bulk Delete action.

Action buttons:

• Download CSV — exports all entries.

• Backfill (Phone list only) — runs the collection rules against historical call data. Configure a date range (Last 7 days / Last 14 days / Custom Range) and optionally filter by specific Publishers, Campaigns, Buyers, or Targets. Shows a success count ("Done! Processed X calls, added Y phone numbers.") or a timeout notice if the job runs long.

• Add phones / Add ZIPs — paste or type values manually (comma or newline separated). Phone numbers are normalized; ZIP codes must be exactly 5 digits.

Delete dataset: available from the action menu. Requires confirmation: "This will permanently delete the list and all phones in it."

Assigning to entities

Once an Audience or Dataset has pings filter enabled, you can assign it to individual relay entities in the entity's Relay settings tab → Audiences and Datasets block.

Adding an Audience or Dataset

Click Audience or Dataset to open a searchable selector. Only items with pings filter enabled appear. Items with a global operator already set are greyed out in the selector — they appear automatically in all entities and cannot be added as local rules.

Allow / Deny operators

Each assigned item has an operator dropdown:

• Allow (green) — pings matching this audience/dataset are allowed through; non-matching pings are suppressed.

• Deny (red) — pings matching this audience/dataset are suppressed.

Default on add: Deny. Every newly added Audience or Dataset starts as Deny.

Global entries

Audiences and Datasets with a global operator set appear automatically in every entity's list. They are locked:

• The operator shows as "Allow · Global" or "Deny · Global"

• The operator dropdown is disabled

• The remove button is hidden (an invisible placeholder keeps the layout)

You cannot add, remove, or change global entries from the entity level. To change a global operator, go to the Audience or Dataset itself on the Audiences page and switch its scope to Local.

Empty state

When an entity has no audiences or datasets assigned (neither local nor global), the block shows: "Not in any audience scope."

Limitations

• Dataset type is fixed at creation. You cannot change a Phone list to a ZIP list or an Anti-spam list after it has been created.

• Only one Anti-spam list per org. The anti-spam dataset type is a singleton — attempting to create a second one is blocked.

• Pings filter must be enabled before assignment. An Audience or Dataset with pings filter disabled does not appear in the entity-level selector and has no effect on traffic.

• Global entries cannot be overridden at the entity level. If an Audience or Dataset has a global operator, its behavior applies to all entities and cannot be changed from the entity's Relay settings tab.

• Attribute-based collection rules require profile enrichment. Without profileEnrichment enabled or the Experimenter role, Attribute rules in dataset collection show "coming soon" and cannot be configured.