Kaliper Documentation

Search...

⌘K

Payload enrichment

Payload enrichment rewrites the buyer request body at relay time using caller profile data. Instead of sending a static body to the buyer's API, the Relay merges in live attribute values — age, ZIP, income, and others — resolved from the caller's phone number.

Important: Available on Dynamic targets only. Requires the Experimenter role.

The payload editor

To open the editor:

  1. Open the Ping Control page and click a Dynamic target row to open its detail window.

  2. In the Overview tab, scroll to the Request config section. A Payload enrichment panel appears below the body field.

  3. Click Payload editor to open the editor dialog.

The editor dialog has two columns.

Left column — template editor

  • Enable/Disable toggle — turns payload enrichment on or off for this target. Changes take effect immediately on save.

  • Add Attribute Tag dropdown — inserts a Handlebars placeholder at the cursor position in the template.

  • Template textarea — write your payload template using Handlebars syntax. Attribute values are referenced as {{profile.fieldName}}. The template must be valid JSON; a red error indicator appears if the JSON is malformed and blocks saving.

Right column — preview

  • Active body template — shows the result of merging the current template into the target's original request body. This is what the buyer receives.

  • Sample data toggle — when on, substitutes sample caller profile values into the placeholders so you can see a realistic merged output without a live ping.

  • Fire test ping (disabled) — this button exists in the UI but is not yet active. It is labeled "Coming soon."

Deep-merge semantics

The template is merged into the original request body, not substituted for it. Only the keys you define in the template are overwritten. Keys in the original body that are not in the template are preserved unchanged.

Example: if your original body is {"leadType": "auto", "phone": "{{phone}}"} and your template adds {"profile": {"age": "{{profile.age}}"}}, the buyer receives both — the original keys and the new profile block together.

Available attribute tags

Tag

Field

{{profile.age}}

Age

{{profile.zip}}

ZIP code

{{profile.state}}

State

{{profile.city}}

City

{{profile.firstName}}

First name

{{profile.lastName}}

Last name

{{profile.incomeMidpoint}}

Household income (midpoint)

{{profile.creditScoreMidpoint}}

Credit score (midpoint)

{{profile.homeOwner}}

Home owner

{{profile.gender}}

Gender

{{profile.maritalStatus}}

Marital status

{{profile.veteran}}

Veteran (household)

{{profile.netWorthMidpoint}}

Net worth (midpoint)

{{profile.language}}

Language (ISO code)

{{profile.hhVehicles}}

Household vehicles (count)

{{profile.hhAdults}}

Household adults (count)

{{profile.vehicles}}

Vehicles (array of make/model/year/VIN)

Limitations

  • Dynamic targets only. Payload enrichment is not available on Fixed or Static targets. The panel is hidden entirely for those target types.

  • Experimenter role required. Users without the Experimenter role do not see the Payload enrichment panel or the editor.

  • "Fire test ping" is not yet available. The button in the editor is disabled and labeled "Coming soon."

  • Profile data is best-effort. Not every caller has a resolvable profile. When a value cannot be resolved, the placeholder is substituted with an empty string or omitted, depending on the field.

‹ Saved views

Audiences ›

© 2026 A-Launch. All rights reserved.

Company

Privacy Policy

Terms of Service

Resources

Documentation

Schedule support call