Traffic Filter

The Traffic Filter controls what users see after they click an ad.

It allows you to:

• Route traffic dynamically
• A/B test different landing pages
• Match intent more precisely
• Improve conversion rates without touching ads

This is a Pro and Enterprise feature. You do not need it to launch or be profitable.

---

What the Traffic Filter Does

The Traffic Filter sits between the traffic source and your Sites.

Instead of sending all traffic to one landing page, you can:

• Split traffic between multiple Sites
• Route users based on conditions
• Test variations without duplicating campaigns

Think of it as a decision layer, not a page builder.

---

When You Should Use the Traffic Filter

Use the Traffic Filter when:

• You have stable traffic volume
• You want to test multiple landing pages
• You want to route traffic based on intent
• You want to optimize without restructuring campaigns

Do not use it during initial testing.

---

When You Should NOT Use the Traffic Filter

Avoid the Traffic Filter when:

• Traffic volume is low
• You are still validating offers
• You do not understand your baseline conversion rate
• You want “one more lever” instead of fixing fundamentals

The filter amplifies structure.
It does not fix bad traffic.

---

Core Use Cases

A/B Testing Landing Pages

You can:

• Assign multiple Sites to one Campaign
• Split traffic between them
• Measure conversion differences

This allows:

• Clean CRO testing
• Faster iteration
• Reduced operational overhead

---

Intent-Based Routing

Traffic can be routed based on:

• Campaign
• Keyword
• Other tracking parameters

Example use cases:

• Brand vs generic keywords
• High-intent vs exploratory searches
• Market-specific variations

This improves relevance without duplicating campaigns.

---

Multi-Site Scaling

Instead of:

• Creating multiple campaigns
• Duplicating ads
• Fragmenting data

You can:

• Keep one Campaign
• Route traffic dynamically
• Maintain clean attribution

---

How the Traffic Filter Works (Conceptual)

At a high level:

1. A user clicks your ad and lands on your external landing page (the router)
2. The Traffic Filter decision engine evaluates the routing rules
3. A Flux site is selected based on the conditions set
4. The user is seamlessly redirected

This happens before the Flux site loads.

---

Setting It Up

The Traffic Filter wizard guides you through every step of the setup — including how to connect your Flux site to your external landing page.

There are three ways to connect:

Option 1 — Full Edge Agent (Recommended)

One CLI command installs everything on your VPS. Highest security — the agent takes over the web server entirely with full control over SSL, routing, and traffic. Requires a cloud server with root access.

Option 2 — Cloudflare Worker

Works with any hosting setup. Runs at Cloudflare's edge for low latency routing. Requires your domain on Cloudflare (free plan works). No server access needed.

Option 3 — PHP Proxy

For servers with PHP support. Works with nginx or Apache. Requires PHP 7.4+ and root access for nginx configuration.

---

Traffic Distribution Logic

Traffic can be:

• Evenly distributed
• Weighted
• Condition-based

Weights should be adjusted slowly and deliberately.

Frequent changes destroy statistical clarity.

---

Validating a Traffic Filter Setup

Before scaling, confirm:

• All target Sites load correctly
• Routing rules behave as expected
• Analytics data is captured
• Conversion tracking still works

Always validate with test traffic.

---

Common Mistakes

Avoid the following:

• Over-segmentation
• Too many rules
• Changing weights too often
• Routing traffic without enough volume
• Treating the filter as a magic fix

Complex filters fail silently.

---

Best Practices

• Start with two Sites
  More is rarely better.

• Let tests run
  Do not rebalance daily.

• Document routing logic
  Especially in team environments.

• Use naming conventions
  Make rules readable six months later.

---

Traffic Filter vs Multiple Campaigns

Use the Traffic Filter when:

• Intent is similar
• Optimization logic is shared
• You want centralized reporting

Use multiple Campaigns when:

• Traffic sources differ
• Bidding strategies differ
• Attribution must be isolated

Choose clarity over cleverness.

---

Summary

The Traffic Filter is a force multiplier.

Used correctly:

• It improves relevance
• It speeds up testing
• It simplifies operations

Used incorrectly:

• It adds noise
• It hides problems
• It slows learning

Earn the right to use it.