Kaliper Documentation
Attribute filters
Attribute filters let you restrict pings based on caller profile data — demographic and geographic attributes resolved from the caller's phone number. Configure them per entity in the Relay settings tab of any Publisher, Campaign, Buyer, or Target detail window.
When a ping arrives, the Relay looks up the caller's profile using the phone number. The profile contains attributes like age range, ZIP, state, estimated income, and others. Attribute filter rules evaluate those values and determine whether the ping should be allowed or suppressed before it reaches buyers. Attribute filtering runs as part of the ping evaluation pipeline alongside caps, source restrictions, and audience suppression.
Important: Attribute filters are available when your org has profile enrichment enabled, or you have the Experimenter role. Without either, the block is visible in Relay settings but all controls are disabled and a "Coming soon" label is shown.
Configuring rules
Open any entity's detail window → Relay settings tab → Attribute filter block.
Adding a rule
Click the Rule button to open the rule type dropdown:
Detector — filter based on the output of a score question. Select a question from your library, then set the required output value.
Attribute — filter based on a caller profile field directly. Select a field from the sub-menu (fields already used in other rules are greyed out). Set a condition value.
You can add multiple rules. All rules use AND logic — a ping must satisfy every rule to pass the filter.
Condition types by question type
Question / Attribute type | Condition input |
|---|---|
Yes/No | Dropdown: YES or NO |
Disposition | Picker: one or more Item Values |
Extract / other | Text input; add multiple accepted values as tags |
Removing rules
Remove all clears all rules at once after a confirmation dialog.
Available profile attributes
Attribute | Description |
|---|---|
Age | Caller's estimated age range |
ZIP | Resolved ZIP code |
State | US state |
City | City |
First name | First name |
Last name | Last name |
Household income (midpoint) | Estimated household income |
Credit score (midpoint) | Estimated credit score |
Home owner | Whether the caller owns their home |
Gender | Gender |
Marital status | Marital status |
Veteran (household) | Whether a veteran is in the household |
Net worth (midpoint) | Estimated net worth |
Language (ISO) | Primary language |
Household vehicles (count) | Number of vehicles in the household |
Household adults (count) | Number of adults in the household |
Vehicles | List of vehicles (make, model, year, VIN) |
Filter operators
Each rule can be set to one of four operator modes that control how edge cases are handled:
Operator | Behavior |
|---|---|
Hard allow | Allows pings where the attribute matches. Suppresses pings where it doesn't match AND pings where the value is unknown or absent. |
Soft allow | Allows pings where the attribute matches AND pings where the value is unknown or absent. |
Strict deny | Suppresses pings where the attribute matches AND pings where the value is unknown or absent. |
Soft deny | Suppresses only pings where the attribute matches. Allows pings where the value is unknown or absent. |
Choose Soft allow or Soft deny when you expect some pings to arrive without resolvable profile data and don't want to block them by default.
Limitations
Requires profile enrichment or Experimenter role. Without either, all controls in the Attribute filter block are disabled. Contact your organization admin or Kaliper support to request access.
Profile data is best-effort. Not every caller has a resolvable profile. Use Soft allow or Soft deny operators to avoid suppressing pings where the attribute cannot be resolved.
All rules use AND logic. A ping must pass every rule in the filter to proceed. There is no per-rule OR logic.
Each attribute can only appear once per filter. Fields already used in a rule are greyed out in the attribute sub-menu.
© 2026 A-Launch. All rights reserved.