Location: Manage Custom Tags from the portal's tag-management surface, then use them in Targets / RTBs and Reporting.
Configured tags can be used in RTB request fields and Advanced Filters. These are related but separate workflows.
1. Dynamic RTB request fields
Use a configured tag as a dynamic value when an RTB endpoint must send call- or publisher-specific data to a buyer.
Create the Custom Tag in the portal and use a consistent lower-case name.
Populate the tag before the RTB request runs, using the publisher request, Call Flow, integration, or another supported source.
Map the tag to the required RTB request field.
Run a controlled test and inspect the outbound request to verify the field name, value, and data format.
Do not rely on tag-name suffixes to determine numeric or string serialization. Verify the actual outbound request format required by the buyer.
2. Advanced Filters
Use a configured tag in Advanced Filters when a Target or RTB endpoint should be eligible only for calls with a matching value.
Confirm the tag exists and is populated before eligibility is evaluated.
Add the tag as an Advanced Filter on the intended Target or RTB.
Choose the operator and expected value.
Test both a matching and non-matching call.
Location data
Moja may derive ZIP or state from caller ID through NPANXX where supported. Treat that as a fallback only. When a buyer requires an exact location value, the integration should send it explicitly and the outbound request should be verified before launch.
Reporting and validation
Use the current Reporting and call-detail surfaces to confirm that the expected tag persisted on the call. Then inspect the relevant RTB request or filter outcome to confirm that the tag was consumed correctly.
Common problems
Blank outbound field: the tag was not populated before the RTB request executed.
Filter never matches: check tag name, lower-case casing convention, value format, and runtime presence.
Wrong data type: compare the actual outbound payload with the buyer's specification instead of inferring type from the tag name.
Wrong ZIP/state: send explicit values when buyer eligibility requires exact location data.