Kaliper Documentation

ZIP enrichment

ZIP enrichment resolves missing ZIP codes from caller phone numbers at relay time. When a ping arrives without a valid ZIP — or with a ZIP that doesn't match the phone's area — the Relay looks up the ZIP from the phone number and injects it into the outbound buyer payload before dispatching.

How it works

  1. A ping arrives at the Relay with a phone number and either no ZIP or an unverifiable ZIP.

  2. The Relay performs a lookup against Kaliper's enrichment database using the phone number.

  3. If a ZIP is found, it is injected into the payload sent to the buyer. The original ZIP the publisher sent is preserved separately.

  4. The enriched ZIP appears in the Pings page with a sparkle icon (✦) next to it. When you open a ping's detail panel, you see both values: the original ZIP and the enriched ZIP side by side.

  5. The Pings distribution card on the Ping Control page shows a count and percentage of enriched pings for the current filter.

Enrichment happens at relay time — before the buyer request is sent — not at display time. The buyer always receives the enriched value; the original is only visible in Kaliper's UI.

Enabling

ZIP enrichment is an org-level setting. When enabled, it applies to all relay traffic across your organization — you cannot enable it per-publisher or per-target.

You can enable it from two places:

  • Ping Control page: the Pings distribution card shows a "No ZIP: X%" indicator with an Enable ZIP enrichment button when enrichment is off.

  • Pings page: the same card and button appear in the distribution section.

Important: ZIP enrichment requires the OrgOwner role to enable. Other roles can see the button but cannot confirm the action.

Limitations

  • No in-app disable flow. Once enabled, ZIP enrichment cannot be turned off from the Kaliper UI. Contact Kaliper support if you need to disable it.

  • Enrichment is best-effort. Not all phone numbers have a resolvable ZIP. Pings where no ZIP can be found are dispatched with whatever the publisher originally sent.

  • Interaction with Restrict Invalid ZIP. If you have Restrict Invalid ZIP enabled on a buyer or target, the validation runs against the enriched ZIP — not the original. This means a ping that would have been blocked for a missing ZIP may pass after enrichment. Enabling both settings together is complementary: enrichment fills in the ZIP, then the restriction validates it.

© 2026 A-Launch. All rights reserved.