If you are running ads in a restricted category and you do not have traffic filtering in place, your destination page is visible to everyone who clicks your ad. That includes Meta’s automated review crawlers, manual reviewers, competitor intelligence tools, and ad verification vendors that platforms hire to audit advertiser compliance. Every one of those visitors sees exactly what your buyers see.

For most advertisers in unrestricted categories, this is fine. For high-risk advertisers running offers that require a separation between what the platform reviews and what the actual buyer experiences, it is the most direct path to a banned account.

Traffic filtering is not an advanced tactic. It is the minimum viable infrastructure for any high-risk operation running paid traffic.

What traffic filtering actually is

Traffic filtering is a decision layer that sits between your ad click and your destination page. Every visitor that clicks your ad passes through this layer first. The layer evaluates a set of signals about that visitor and makes a binary decision: send them to your real offer, or redirect them to a safe, policy-compliant page.

The visitors who get redirected never see your real offer. They see what is called a white page — a clean, legitimate-looking page that would pass any platform review. The visitors who pass the filter reach your actual destination, your black page, as normal.

From the platform’s perspective, every review of your ad leads to the white page. From your buyer’s perspective, nothing changes. The separation is invisible to everyone it needs to be invisible to.

Why it matters more than your creative

Most advertisers in restricted categories focus their energy on the creative: writing compliant copy, choosing safe images, avoiding prohibited claim patterns. All of that matters. But a perfectly compliant creative that sends traffic to an unfiltered destination page solves half the problem and ignores the other half.

Platform review does not stop at the ad. When Meta’s system flags an account for manual review, a reviewer follows the ad click to the destination. If they reach your real offer directly, the review finds exactly what you were trying to avoid showing them. The creative was compliant. The destination was not. The account gets banned.

Filtering protects the destination, not just the creative. Both layers need to be correct for the operation to hold under review.

The signals a filter evaluates

A basic filter checks a small number of signals per visitor. A well-configured filter checks several simultaneously and requires all of them to pass before allowing access. Here are the primary signals and what each one catches.

Getting started with Keitaro

The most accessible tool for setting up traffic filtering as a high-risk advertiser is Keitaro, a self-hosted tracker that handles both the filtering logic and campaign tracking in one platform. It is widely used in performance marketing, well-documented, and gives you direct control over your filter rules without relying on third-party services that could change their terms or go offline.

At its core, Keitaro works by routing each incoming click through a campaign flow you define. You set the filter conditions, point the “pass” path to your real offer and the “fail” path to your white page, and Keitaro handles the evaluation and redirect on every click. The setup process involves installing Keitaro on your own server, configuring your filter rules, and replacing your direct destination URL with your Keitaro campaign URL in the ad.

Custom tracking: the part most advertisers skip

Filtering controls who reaches your destination. Tracking controls what data flows back to the ad platform about those visits. The two need to work together, because a correctly filtered operation can still expose itself through a poorly configured pixel.

The specific risk is this: a standard Meta pixel fires a conversion event that includes the URL of the page where it fired. If your pixel is installed on your real offer page, Meta receives that URL every time a conversion fires, bypassing your filtering entirely. The filter kept the reviewer away from the page. The pixel sent the page to Meta anyway.

The correct setup fires all tracking events on the white page domain only, with server-side events as the primary data layer. Your real offer page carries no pixel code. Conversion signals flow back to the platform with full attribution accuracy, but the destination URL in those signals is always the white page, never the real offer.

Keitaro handles some of this with its postback and S2S tracking functionality, but the full implementation, particularly the server-side event layer and white-page-only pixel firing, requires additional configuration beyond a standard Keitaro install.

The white page: not a placeholder

The white page is the destination every reviewer, crawler, and non-qualifying visitor reaches. Most advertisers build the minimum possible version: a thin page with some generic content that technically makes sense as a landing page. This approach works until it doesn’t.

A white page that looks obviously constructed, that has no real content, no navigation, no coherent purpose, and no reason to exist as a standalone page, is itself a signal. Manual reviewers who land on a white page are looking for exactly this kind of hollow experience. A white page that looks genuinely real, with actual content relevant to the ad angle, functional navigation, and a believable reason to exist, passes review at a higher rate and for longer.

The white page should match the creative angle of the ad that points to it. If your ad targets crypto-native audiences, your white page should be a plausible crypto content destination. If your ad targets wellness audiences, your white page should be a plausible wellness content destination. A mismatched white page, where the ad and the landing page feel disconnected, is a flag in itself, both to automated systems and to manual reviewers.

The white page is not a technicality. It is half of your compliance strategy.

How deep does your setup need to go?

The right level of filtering sophistication depends on the category you are advertising in, the volume you are running at, and the platforms you are using. A basic Keitaro setup with standard geo and IP filtering is meaningfully better than nothing and is the right starting point for advertisers who are new to filtered traffic operations.

As volume scales and as the platforms you run on become more sophisticated in their review methods, the filtering layer needs to evolve with them. The review patterns that a basic Keitaro configuration catches today are not the same as the ones that will be used to audit your account next quarter. Filtering is not a set-and-forget installation. It is an ongoing technical discipline.

The specifics of how a high-performance filtering layer is built, how it is tuned to specific platform review patterns, how the tracking architecture is structured to eliminate pixel-level exposure, and how the white page is designed and maintained, are the details we do not publish. They are what we build for clients, and they are what separates an operation that holds at scale from one that holds until the next review cycle.