Choose your destinations
Add your main route under Default Paths. Choose:
Keep at least one enabled default path for visitors who do not match a rule.
Build a reliable default first
- Open 3. Rotator in a campaign and choose Campaign-only Rotator. For a shared rotator, open Rotators, click Create, and enter Rotator name and Country.
- Under Default Paths, click Add Default Path if needed, then select the path.
- Enter Path name, choose Path action, and select the destinations.
- Set positive whole-number weights. Keep the path and destinations enabled.
- Save. If you created a shared rotator, select it in the campaign.
- Open the campaign link and check the destination.
Use weights to express proportions
Weights are relative. They do not need to add up to 100.
Small samples can differ from these shares. Change the weights as you compare results, or disable a destination to stop sending traffic to it.
Any landing in a path can lead to any offer in that path. For Landing A → Offer A and Landing B → Offer B, create two paths. Use path weights to split traffic between the pairs.
Use Redirect to split traffic between landing pages. With Direct script, the ad opens a fixed page and you can split traffic between its offers.
Add a conditional route
For example, send mobile visitors to a shorter landing:- Under Rule-based Paths, click Add Rule.
- Add a Device Type condition and select the mobile value.
- Set the rule’s path to the short landing and an offer.
- Keep the standard landing in Default Paths.
- Save the campaign or shared rotator.
Verify both the special route and fallback
Test a visit that matches the rule and one that should use Default Paths. Check their destinations and the path, landing and offer breakdowns in the campaign report.Block selected traffic
Set Path action to Block request and choose 403 Forbidden or 404 Not Found under Response. This path needs no landing or offer. Blocked visits remain in reports under the path. With Direct script, the page has already opened and remains visible.Use bot, VPN and prefetch conditions
Use bot, VPN and prefetch conditions
- Is Bot matches detected bots and non-browser clients. Use Bot Category for a category such as AI Crawler or Security. A blank category does not mean the visitor is human.
- Is VPN → is → true matches detected VPN or Tor traffic. false means neither was detected.
- Is Prefetch → is → true matches recognized prefetch on new visits. Prefetch loads a page before a visitor opens it. It does not by itself mean the visitor is a bot, and this condition excludes browser prerender.