Kaliper Documentation

Clone protection

Overview

Clone protection stops a buyer from paying twice for the same caller who shows up in two verticals at once. It is a per-buyer setting: you choose how long Kaliper remembers a phone number, and whether a clone is let through or blocked.


What is a clone?

A clone is a ping that reaches a buyer with a phone number the buyer already received from a different vertical within the detection window. For example, a caller who submits an auto insurance form and, ten seconds later, a home insurance form reaches the same buyer twice, once per vertical. The second ping is the clone.



You can choose one of two actions:

  • Let through (default): the clone is delivered as usual and marked as a clone in the ping details.

  • Block phone number: the clone is dropped, and the phone is blocked for that buyer in every vertical until the window ends.

A repeat of a phone within the same vertical is not a clone. Your deduplication settings handle it.

How detection works

Kaliper remembers, for each buyer, the first vertical each phone number arrived from. Any ping for the same phone from another vertical before the window ends is a clone.¡

  • Scope is the buyer, not the target. All of a buyer's targets share one memory, so a phone sent to target A in one vertical and target B in another is still a clone.

  • The vertical comes from the campaign. A campaign with no vertical counts as a vertical of its own.

  • The window starts with the first ping. Later pings from the first vertical do not extend it. When the window ends, the next ping for that phone starts a new window.

  • Only valid phone numbers are checked. A ping without a full 11-digit phone number is never treated as a clone.

  • Duplicates are not counted twice. A duplicate of a ping that was already delivered to the same target is handled by deduplication, not checked again.

  • Detection fails open. If Kaliper cannot check a phone, for example during a brief storage outage, the ping is treated as not a clone and delivered normally.

Settings

Clone protection is set on the buyer. Every buyer starts with Let through and a 15-second window.

To change it:

  1. Open Ping Control and select the buyer to open its details panel.

  2. Click the Clones row. It shows the current setting, for example "Let through (15 sec) (default)" or "Block for 30 sec".

  3. In the Clones dialog, enter the Detection window in seconds.

  4. Choose what happens to a clone: Let through or Block phone number.

  5. Click OK.

Setting

Values

Default

Detection (s)

Whole seconds, 10 to 86,400 (24 h)

15

What happens to a clone

Let through · Block phone number

Let through

A window outside 10 to 86,400 seconds, or one that is not a whole number, is rejected with the message "Detection must be a whole number of seconds, 10–86400".

What happens to a ping

The clone check runs before any other step for the buyer, so a blocked ping costs nothing: no enrichment, no cap or pacing slot used, no request to the buyer.


Let through

Block phone number

The first clone

Delivered to the buyer, marked "Clone: Yes"

Dropped, and the phone becomes blocked for the buyer

Later pings for that phone, any vertical

Delivered normally (clones marked)

Dropped until the window ends, including pings from the first vertical

Response to the publisher

The buyer's normal response

HTTP 422 with code clone_blocked

Ping status

The normal outcome

Suppressed › Clone, reason "Clone"

Counted in Clones dropped

No

Yes

How long a block lasts. A block runs for one full window, starting from the clone that triggered it. Blocked pings that arrive later do not extend it. When it ends, the phone is accepted again and the next ping starts a new window.

Blocked is not the same as clone. Once a phone is blocked, a ping from its first vertical is dropped too. That ping is not marked as a clone, because it is not one, but it still counts in Clones dropped.

Monitoring

Dropped clones show up in Ping Control in four places. Clones that were let through are visible only on the ping itself.

Where

What you see

Ping Control table, Clones droppedcolumn (Suppression group)

Pings dropped by clone protection, as a count or as a share of original pings. Add it from the column picker under Suppressed: Clone.

Status bar above the pings list

A Clone segment in the suppression part of the bar

Status filter

Suppressed › Clone, also included in Any Suppressed

Buyer details, Clones row

The buyer's current setting and how many pings it has dropped

Ping details

Clone: Yes — the buyer already got this phone from another vertical, shown for every clone in either mode

The Clones dropped column is also included in the CSV export.

Example

Buyer Acme Leads uses Block phone number with a 30-second window. One phone number arrives four times:

Time

Campaign (vertical)

Result

Why

0 s

Auto campaign 1 (Auto)

Delivered

First ping. Auto becomes the phone's first vertical.

5 s

Home campaign (Home)

Dropped, 422 clone_blocked, marked as clone

Another vertical within the window. The phone is now blocked until 35 s.

10 s

Auto campaign 2 (Auto)

Dropped, 422 clone_blocked, not marked as clone

The phone is blocked in every vertical.

40 s

Home campaign (Home)

Delivered

The block has ended. Home becomes the first vertical of a new window.

A different phone number sent to Acme Leads at any point is not affected. Acme Leads receives two requests in total, and the Clones dropped column shows 2.

With Let through, all four pings would be delivered, and only the 5 s ping would be marked as a clone.

FAQ and limitations

Can I set clone protection per target or per campaign? Not at the moment. It is a buyer setting and covers all of that buyer's targets.

Does changing the setting affect phones already being tracked? The new action applies from the next ping. A window that is already running keeps the length it started with.

Why does Clones dropped show 0 when I know clones are arriving? The buyer is probably on Let through. Clones are then delivered and marked only in the ping details; nothing is dropped.

Why was a ping from the original vertical dropped? The phone was blocked by an earlier clone. While a block lasts, it applies to every vertical.

Can I filter the pings list to clones that were let through? Not yet. The status filter covers dropped clones only. Let-through clones are marked in each ping's details.

What should publishers do with a 422 clone_blocked response? Treat it as a final rejection for that buyer. Resending the same phone during the block returns the same response.

© 2026 A-Launch. All rights reserved.