Location: RTB Campaigns β Create / Edit Page
βLast Updated: October 2025
π Overview
Advanced Filters let you control which traffic is eligible for each RTB campaign by allowing or blocking calls based on state, ZIP code, publisher, and configured Custom Tags.
Filters can be combined in any configuration β for example, allowing traffic from specific states while blocking certain ZIP codes, publishers, or Custom Tag values β all directly from the RTB campaign page. This enables fast, precise traffic control without backend or schema changes.
βοΈ How Advanced Filters Work
Advanced Filters evaluate incoming RTB traffic at execution time and determine whether a call is eligible to enter the campaign.
You can configure rules to:
β Allow or π« Block calls by:
State
ZIP code
Publisher
Custom Tag values
Combine multiple rules for precise targeting
Update filters at any time without redeploying campaigns
π¦ Execution Timing: Filters are evaluated automatically whenever the RTB executes.
π§ Filter Capabilities
Flexible Rules
Create allow or block rules for State, ZIP, Publisher, and Custom Tags
Use rules independently or together
Combination Support
Mix multiple conditions for granular control
Example: Allow CA + NV, block specific ZIP ranges, exclude select publishers
Real-Time Validation
Filters are validated when saving the campaign
Invalid or incomplete configurations are flagged immediately
Reusable Configuration
Filters are saved with the campaign
You can update them at any time as traffic patterns change
π Configuration Requirements
Advanced Filters require the fields used in the filter condition to be available at RTB execution time. Common built-in fields include:
statezippublisher_id/publisher_nameConfigured Custom Tags
These values must be available at RTB execution time. You can provide state/ZIP using either of the methods below. For arbitrary publisher-supplied values, define them as Custom Tags first, then select those tags in Advanced Filtering.
π Option 1: Manual Parameter Passing
Use this approach when your inbound RTB already includes location data.
Pass
stateandzipas URL parameters in the inbound RTB requestCreate a tag as the value for one of your parameter keys
The tag will be overwritten with the
state/zipvalues from the RTB URL parameters
π¨ Use Case: Best when the upstream system already knows the callerβs location.
π Option 2: Caller IDβBased (Automated) Resolution
Use this approach when location data is not explicitly passed.
Pass only the
caller_idin the inbound RTB requestAdd a
zipkey with a tag placeholder (for example,[ZipCode])Moja automatically resolves ZIP and State using NPANXX lookup based on the caller ID
π© Automation: No manual location handling required β state and ZIP are derived automatically.
Both options ensure Advanced Filters receive the required data for accurate eligibility decisions.
π Works with Custom Tags
Advanced Filters integrate seamlessly with Custom Tags.
Use built-in tags like
[STATE]or[ZIP_CODE]inside filter conditionsUse Custom Tags for publisher-supplied values such as
sub_id,lead_type,traffic_source,vertical, or other custom fieldsTags resolve dynamically from session, caller context, or inbound request parameters
Enables adaptive, data-driven routing logic directly within the RTB
π§ Result: Predictable, flexible routing even under complex targeting rules.
π― Why This Matters
Advanced Filters give campaign managers fine-grained control over RTB traffic.
They help you:
Focus spend on high-performing regions and publishers
Maintain compliance with geographic restrictions
React instantly to changes in traffic quality
Avoid unnecessary routing to low-value or restricted sources
All without engineering intervention.
π‘ Example Use Cases
Compliance: Block calls from restricted states
Performance: Exclude ZIP codes with poor conversion rates
Partner Management: Accept traffic only from approved publishers
Custom Values: Route or block traffic based on Custom Tags such as
sub_id,lead_type,traffic_source, orverticalDynamic Routing: Combine tag-based state, ZIP, publisher, or custom-value resolution with filters for adaptive targeting
π Getting Started
Go to Targets / RTB β RTBs
Open an existing RTB or create a new one
Scroll to the Advanced Filters section
Click Add Condition and choose State, ZIP, Publisher, or Tag
Set each rule to Allow or Block
Save the RTB
β Filtering and tag resolution run automatically during RTB execution β no additional setup required.