Campaign filters
This article shows how to build campaign filters that accept or reject leads by field rules. Filters protect buyer quality and stop junk before distribution spends attempts on the wrong traffic.
Start small. Order matters, and a single broad reject can block more volume than you expect.
What are campaign filters?
Filters are rules evaluated against lead data. When a rule matches, it either ACCEPTs or REJECTs. Filters can run at several levels so global policy and party-specific exceptions stay separate.
| Level | Applies to | Typical use |
|---|---|---|
| Global | All leads in the campaign | Geo allow lists, obvious junk rejects |
| Supplier | Leads from one supplier | Source-specific quality rules |
| Buyer | Leads considered for one buyer | Buyer geo or attribute requirements |
| Traffic Source | Leads from one affiliate channel | Channel-specific accepts or blocks |
Filters stop at the first matching rule in evaluation order. That is why rank and output both matter.
Prerequisites
- An existing campaign with fields defined
- A clear list of must-have and must-block conditions
- Buyers, suppliers, or traffic sources already created if you need non-global levels
Add filters
- Go to Campaigns and open the campaign.
- Open the Filters tab.
- Find the section for the level you need (Global, Supplier, Buyer, or Traffic Source).
- Click Add filter.
- For non-global levels, choose the supplier, buyer, or traffic source scope.
- Select the field (key) to evaluate.
- Choose the condition (equals, has one of, greater than, contains, and similar options shown in the UI).
- Enter the comparison value or values.
- Set the output to ACCEPT or REJECT.
- If the UI offers a payout on an accept match, set it only when that rule should change price.
- Click Save.
- Drag to reorder when a rule must be evaluated earlier or later.
- Review Rule Analyzer warnings and fix anything that looks unintentional.
- Send a test lead that should match, and one that should not, then confirm outcomes on the lead timeline.
How to think about ACCEPT vs REJECT
| Output | When to use | Watch out for |
|---|---|---|
| REJECT | Hard no for matching leads | Over-broad values block good traffic |
| ACCEPT | Explicit allow, sometimes with payout | Order still matters if a later reject never runs |
If no filter matches, leads typically continue by default. Do not assume an empty filter list means "reject everything."
Rule Analyzer (high level)
Rule Analyzer surfaces configuration warnings in the filter UI, such as orphaned scoped filters, missing fallback-style setups, or accept rules that look incomplete. Treat it as a review assistant. It does not replace reading your own business rules or testing with sample leads.
Tips and gotchas
- Build fields before filters. Filters need stable field names.
- Put the most specific reject rules where you intend them. A global reject affects everyone.
- Buyer filters can make a buyer look "broken" on the timeline when they are simply ineligible.
- After reordering, re-test. First match wins.
- For repeated reject patterns across many leads, switch from one timeline to Rejection Reasons overview.
Expected result
The Filters tab shows intentional rules at the right levels, Rule Analyzer is clear of accidental warnings you care about, and test leads accept or reject exactly as designed.
Frequently asked questions
Do I need filters on day one? Not always. Required fields and one trusted supplier can be enough. Add filters when you know which junk to block.
Why did my global accept not help a buyer? Buyer-level rules and delivery eligibility still apply. An accept at one stage does not force a specific buyer to purchase.
Can filters set different payouts? Accept filters may support conditional payout in the UI. Use that when price should change for matching attributes, and document the rule for your team.
What is the difference between a field being required and a filter? Required fields enforce presence and basic type validation. Filters enforce business rules on values that already arrived.
How do I debug one surprising reject? Open the lead timeline first. It names the rule path more clearly than a KPI card.
Should supplier and traffic source filters duplicate each other? Prefer one clear home for each rule. Duplicate logic at multiple levels becomes hard to reorder safely.
Related articles
Comments
No comments yet — be the first to share your thoughts.