Datasets

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

A Dataset is a collected list of phone numbers or ZIP codes, plus the rules that decide which pings it suppresses or allows.

Audiences have been removed. Earlier versions of Kaliper grouped Datasets into Audiences. Every Audience function is available directly on a Dataset, so the Audience object and its page no longer exist.

The Datasets page

The Datasets page (/home/relay/datasets) lists all datasets in your org with these columns:

Click New dataset to open a type selection:

Type cannot be changed after creation. Click any row to open the dataset detail panel on the right.

Dataset detail panel

Settings section: name field, saves on blur.

Limits section (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 section (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 section (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.).

• Remove all clears all rules.

Ping Control traffic section: controls whether this dataset actively filters pings.

• Disabled option, When disabled, the dataset keeps collecting entries but has no effect on traffic.

• Org-wide mode: a single operator applies to your entire org.

• Selection mode: entity-level rules. Add Publishers, Campaigns, Buyers, or Targets. For each entity added, set the operator to Deny matches only or Deny all except matches. A Remove all button (trash icon) clears all entity rules at once.

Captured entries section (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 (ellipsis). Requires confirmation: "This will permanently delete the list and all phones in it."

Assigning to entities

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

Adding a Dataset

Click Dataset to open a searchable selector. Only datasets with pings filter enabled appear. Datasets 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 dataset has an operator dropdown:

• Deny matches only (hexagon outline icon): drops only the pings that have the data matching the dataset. Default option.

• Deny all except matches (hexagon with x icon): drops all the pings that do not have metadata matching the dataset. Use with caution.

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. A 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 a Dataset has a global operator, its behavior applies to all entities and cannot be changed from the entity's Relay settings tab.