Overview

What you're getting

You're routing thousands of pings a day between Publishers and Buyers, but most of what happens to them never crosses your desk — bad pings burn Buyer relationships, duplicates get handled wrong, ZIPs you don't watch have no coverage.

Kaliper Ping Control sits between your call tracking platform and every Buyer. It logs every ping with full request and response, stops the ones that shouldn't go through, enriches the ones that do, and recovers revenue from duplicate pings without hitting a Buyer's API twice.

All of it is happening in real time. You can dig into any ping to see exactly which rule fired, adjust any rules on the fly, and watch your traffic by any angle: Publishers, Buyers, Campaigns, Targets, Sub IDs, ZIPs and more.

How it works

The whole process runs without any manual steps.

1. The Relay receives the ping from the Publisher.

   The Kaliper Relay (Relay) is a real-time routing engine that connects your call tracking platform to your buyers. When a ping arrives, the Relay checks it against your configured rules — source restrictions, deduplication, volume caps, and suppression lists — enriches it with caller profile data where applicable, and dispatches it to the buyer's API. Every ping's outcome, along with the full request, response, and rule trace, is recorded automatically. See Ping processing pipeline for the full sequence.

2. The ping is evaluated against the rules on the Publisher, Campaign, Buyer, and Target it touches — source restrictions, deduplication, suppression audiences, attribute filters, and volume caps and more. Anything that shouldn't reach a Buyer is stopped here.

3. The ping is enriched if applicable. Missing ZIPs are resolved from the caller's phone number; Dynamic targets can merge caller profile data (age, income, state, and so on) into the outbound body so Buyers can bid with full context.

4. The Relay calls the matched Buyer's API and waits for a bid response within the auction window.

5. The Relay records the result. See Inspecting pings for the full status list and field reference.

   • Ping status — Accepted if a Buyer bid in time, otherwise the rule or outcome that cut it off (No Coverage, Capped, Suppressed, etc.).

   • Stat counts — Ping Control page updates immediately, by entity.

   • Per-ping detail — full request, response, and rule trace appear on the Pings page.

How to get set up

Step 1 — Relay: enable on your targets

Turn on the Relay on the Targets you want to route through Kaliper. With nothing else configured, every ping addressed to a Target gets logged and dispatched — data starts flowing into the Ping Control page immediately.

→ Setting up Relay

Step 2 — Control rules: add as the traffic shows you

Caps, deduplication, source restrictions, suppression Audiences, and Attribute filters all live in each entity's relay settings. Automatic suggestions are on the way.

→ Caps and deduplication

→ Restricting traffic

→ Audiences and Datasets

→ Attribute filters

Step 3 — Enrich what reaches your buyers

Two enrichments make the pings you do dispatch more valuable. ZIP enrichment fills in missing ZIPs from the caller's phone number — pings that would have been rejected as No Coverage for missing ZIP get a chance to bid. Payload enrichment merges caller profile attributes into the outbound body so Buyers can target with the full picture.

→ ZIP enrichment

→ Payload enrichment

Step 4 — Monitor, debug, and find gaps

The Ping Control page is your live view of volume, acceptance, and revenue per entity.

→ Monitoring pings

The Pings page is where you go when you want to know why a specific ping got the status it did.

→ Inspecting pings

The Coverage map shows your ZIP-level acceptance — where you have Buyer demand and where you don't.

→ Coverage analysis