️ Advanced Filters for Targets and RTBs

Location: Targets / RTBs → select a Target or RTB → Advanced Filters

What Advanced Filters do

Targets and RTB endpoints can apply Advanced Filters using configured custom tags and supported system values before routing a call or sending a buyer request.

A filter is only useful when its runtime value exists and has the expected format. Saving a rule does not guarantee that the publisher, Call Flow, integration, or other upstream source will supply the required value.

Before creating a filter

1. Identify the exact value required by the buyer or route.

2. If it is publisher-specific or otherwise custom, define it as a Custom Tag in the portal first.

3. Use a consistent lower-case tag name across collection, ingestion, filtering, RTB request templates, and reporting.

4. Confirm the value is present on a controlled test call before relying on the filter for live traffic.

Create an Advanced Filter

1. Open the intended Target or RTB endpoint.

2. Open Advanced Filters and add the required condition.

3. Select the supported system value or configured Custom Tag.

4. Choose the operator and expected value carefully.

5. Save, then run positive and negative test cases.

ZIP and state values

Moja may derive location from caller ID through NPANXX where supported, but this is a fallback. It is not a substitute for publisher-supplied location data when buyer eligibility depends on an exact ZIP or state. Integrations should send required location values explicitly.

Troubleshooting

• Rule saved but never matches: verify the tag exists at runtime, the name and casing match, and the value is not blank or malformed.

• Unexpected eligibility: inspect every rule and its AND/OR relationship, then test with known values.

• Location mismatch: compare the explicitly supplied ZIP/state with any derived caller-ID location.

• Custom value unavailable: create and populate the Custom Tag before using it in the filter.