Kaliper Documentation

Pings

The Pings page is a near-real-time log of individual ping events. Use it for live debugging, investigating a specific phone number or source, and tracing exactly what happened during a call.

Unlike the Ping Control page (which shows aggregated stats), the Pings page shows one row per ping with full detail available on click.

Filtering pings

By time

Option

Window

Current Hour

From the top of the current hour

Last 60 minutes

Rolling 60-minute window (default)

Last 6 hours

Rolling 6-hour window

Last 12 hours

Rolling 12-hour window

Today

From midnight to now

Custom Date

A single calendar day — pick one date, not a range

By entity

Use the entity selectors to filter pings by Publisher, Campaign, Buyer, or Target. Multiple selections within the same category are combined with OR logic.

By ping data

Filter

What it does

ZIP codes

Show only pings from specific ZIP codes

Phone

Show only pings from a specific phone number

Source IDs

Show only pings with specific Source IDs

Status

Multi-select: filter by one or more ping statuses

Sub IDs

Show only pings carrying specific Sub-IDs

Invalid ZIPs only

Show only pings where the ZIP was invalid or missing

Invalid phones only

Show only pings where the phone number was invalid

Late bids only

Show only pings where the buyer responded after the auction window closed

No sub ID only

Show only pings with no Sub-ID

Pings distribution

Two cards appear above the table when the current filter is not "narrow": a Pings distribution stacked bar showing ping counts by status, and a ZIP enrichment card. When ZIP enrichment is enabled the card shows the count and percentage of enriched pings. When it is disabled the card shows the percentage of pings with no valid ZIP and an Enable ZIP enrichment button.

A filter is considered narrow when any of the following are active: ZIP codes, Phone, Source IDs, Status, Sub IDs, Invalid ZIPs only, Invalid phones only, or No sub ID only. When a narrow filter is active, the distribution bar is hidden.

Important: Late bids only does not trigger the narrow mode — the distribution bar remains visible when only that filter is on.

Group by auctions

The Group by auctions toggle switches from per-ping rows to per-auction rows. An auction groups all pings that share the same Source ID.

When an auction row is expanded, a summary panel shows:

  • Source ID

  • First and last ping timestamps

  • Ping count

  • Accepted count out of total (e.g. "Accepted 1/3")

  • Bid range (min–max across all pings)

  • Whether any ping was a late bid

  • Phone, ZIP, Publisher, Campaign, Sub-ID (taken from the first ping)

Below the summary, the Pings block lists all individual pings in that auction.

Exporting

Click Download CSV to export the current filtered ping list.

The table

Each row is one ping.

Column

Notes

Timestamp

When the ping was received

Phone

Caller phone number

ZIP

ZIP code. If the original ZIP is missing but an enriched ZIP is available, the enriched value is shown in its place with a sparkle icon. If the original ZIP is present it is shown as-is — no sparkle, even if enrichment data also exists.

Status

Ping status

Bid

Bid amount returned by the buyer

Call

Phone icon shown when a call is linked to this ping. This is a visual indicator only — clicking the column does not open the call. To open the call, click the row to open the ping detail, then use the Open Callbutton inside the Ping Data section (requires CQC access).

Target

Target name

Buyer

Buyer name

Campaign

Campaign name

Publisher

Publisher name

Latency

Response time in ms; shown in red when the bid was late

Source ID

Publisher's identifier for this ping

Sub ID

Sub-publisher identifier

Duplicates

Count of duplicate pings from the same Source ID

Ping detail window

Click any ping row to open its detail panel on the right.

Details section

Field


Time

Timestamp of the ping

Source ID

Publisher's ping identifier

ZIP

ZIP code (original)

Phone

Caller phone number

Publisher

Publisher name

Campaign

Campaign name

Buyer

Buyer name

Target

Target name

Status

Ping status

Bid

Bid amount

Buyer Response Code

HTTP response code from the buyer

Ping data section

  • Call Available banner — appears when a call recording is available for this ping. Includes an Open Call button that opens the call in Call Quality Control (requires CQC access and the CallsManager role).

  • ZIP enrichment pair — when the zipEnriched field is set, two rows appear instead of one: "ZIP (original):" (shown as "—" because the original was absent) and "ZIP (enriched):" with the enriched value.

  • Duplicates — shown when duplicate Source IDs exist. Displays the first duplicate Source ID by default; click Show All (N) to expand the full list and Hide to collapse it again.

  • Request — full outbound request to the buyer: URL, method, headers, and body.

  • Response — full buyer response: HTTP code, response time, auction validity flag, and body.

Coverage Score (CS)

The field is labeled CS in the UI and is shown at 50% opacity — this signals it is an internal diagnostic field, not a user-facing metric. Clicking it reveals the raw diagnostic JSON used by the Kaliper team to investigate routing and bid decisions. Do not base operational decisions on this value.

Reporting parsing issues

If the ping detail shows unexpected or garbled data, the Report parsing issue button sends feedback directly to the Kaliper team. Submitting a report has no effect on the ping's status or any related calls.

Limitations

  • The Pings page is near-real-time, not live. Ping records are written asynchronously — there is a brief delay between when a ping is processed and when it appears in the table.

  • Pings blocked at validation or source restriction do not appear. No record is created for pings that fail first stages of the Ping processing pipeline.

© 2026 A-Launch. All rights reserved.