Campaign use cases
Designing Adult Traffic Filters Around Source Quality
Vertical labels do not replace analysis; each campaign still needs identifiable inventory and destination rules grounded in its actual market.
Document market and destination policy
List supported countries, age and content requirements handled outside the router, device expectations, and destination ownership. Traffic routing should implement the approved path, not make legal or platform-policy conclusions for the operator.
Separate sources and placements
Carry network, publisher, zone, and campaign identifiers whenever available. Adult inventory can vary sharply between placements, so source-wide settings often hide the segment that actually needs attention.
Combine device and network context
Review country, language, mobile environment, ASN, ISP, proxy indicators, repeated clicks, and missing context together. Avoid treating privacy tools or a shared carrier address as automatic evidence of abuse.
Protect against mismatched pages
Incorrect locale, broken mobile media, redirect loops, and unsupported markets can create poor outcomes even when routing is accurate. Keep page defects distinct from traffic classification in incident notes.
Run a market-specific review
Test both destinations from representative devices and regions, verify source attribution, and sample live decisions by placement. Reassess filters after buying strategy changes because yesterday's traffic mix may no longer describe the campaign.