Kaliper Documentation
Setting up Relay
Once at least one Target is enabled, Ping Control routes pings through the Kaliper Relay.
Enabling Relay
Bulk enable
On the Ping Control page, check the boxes next to the targets you want to change.
In the action bar at the top, click Enable selected.
From a target's detail window
On the Ping Control page, click any target row to open its detail window.
In the Overview tab, click Enable relay.
Disabling Relay
Single target: click Disable relay in the target's Overview tab.
Bulk: select target rows and click Disable selected in the action bar.
Sync with your call tracking system runs automatically every 6 hours. As an organization owner, you can also trigger a manual sync anytime from the Account page using the Sync with button.
Target types
Kaliper assigns each target a type automatically based on how it is configured in your call tracking platform. You cannot change the type from within Kaliper.
Dynamic — a standard RTB target. Kaliper forwards the ping to the buyer's endpoint and receives a real-time bid. Full relay configuration is available.
Fixed — the buyer has configured a fixed payout in the call tracking platform rather than bidding in real time. Kaliper uses that amount directly without making a request to the buyer. Relay settings are not available because the bid is predetermined — only statistics are collected.
Static — a non-RTB routing destination that does not participate in real-time ping processing. Most relay options are hidden, and the Enable/Disable button is not shown. Relay state for static targets is managed from within your call tracking platform.
Dynamic | Fixed | Static | |
|---|---|---|---|
Enable / Disable | Yes | Yes | No |
Relay settings (caps, dedup, restrictions) | Yes | — | — |
Payload enrichment | Yes | — | — |
Sub-ID performance | Yes | Yes | — |
Ping statistics | Yes | Yes | — |
Ping-post support
Some platforms use a two-step ping-post model where the buyer first receives a ping (bid request) and then a post (confirmation) after the call connects. Kaliper handles both steps:
Platform | Ping-post mechanism |
|---|---|
Ringba |
|
Retreaver |
|
CallGrid |
|
Trackdrive | Not yet supported — only the initial ping is relayed |
When ping-post is active, Kaliper relays the confirmation back through Relay as well, so both phases are tracked.
Target issues
When a target has a configuration problem, an issue tag appears next to its name in the table and in the detail window.
Issue | Meaning |
|---|---|
URL mismatch | Relay is enabled, but the target's URL in your call tracking platform no longer matches the Kaliper relay endpoint. Pings will not route correctly until the URL is fixed. |
Disabled in platform | Relay is enabled in Kaliper, but the target has been disabled directly in your call tracking platform. Kaliper cannot route pings to a disabled target. |
Still pointing to Relay | Relay is disabled, but the target's URL in your call tracking platform still points to Kaliper. Pings from the platform will arrive but will not be processed. |
Residual configuration | Relay is disabled, but Kaliper's payload modifications are still present in the target's configuration in your call tracking platform. |
All four issue types are critical — each one means pings are either misrouted or not processed as expected.
When an issue appears on an enabled target, a Refresh button appears next to it. Clicking Refresh re-syncs the target's configuration from your call tracking platform — use it after correcting a problem on the platform side.
© 2026 A-Launch. All rights reserved.