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, and/or publisher.
Filters can be combined in any configuration — for example, allowing traffic from specific states while blocking certain ZIP codes or publishers — 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
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, and Publisher
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 two data points to function correctly:
statezip
These values must be available at RTB execution time. You can provide them using either of the methods below.
📌 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 tags like
[STATE]or[ZIP_CODE]inside filter conditionsTags resolve dynamically from session or caller context
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
Dynamic Routing: Combine tag-based state or ZIP 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, or Publisher
Set each rule to Allow or Block
Save the RTB
✅ Filtering and tag resolution run automatically during RTB execution — no additional setup required.