CoreUpdated 2025• 5 min read Updated 2025

Campaign Targeting Rules

Targeting rules let you precisely control which traffic is accepted, redirected, or rejected for a campaign — based on geo, device, OS, ISP, and more.

Overview

While basic targeting sets the default audience for a campaign, targeting rules give you conditional logic to handle specific traffic segments differently. Each rule consists of one or more conditions evaluated against the incoming click, and an action taken when all conditions match.

Common use cases include:

Blocking low-quality traffic from specific countries or ISPs
Redirecting mobile traffic to a separate campaign
Allowing only specific device types or OS versions
Routing traffic from a specific source to a fallback offer

How Rules Work

Rules are evaluated in priority order (lowest number = highest priority). When an incoming click is received:

Each rule is checked in priority order.
The first rule whose conditions all match is applied.
No further rules are checked after a match.
If no rule matches, the click is rejected by default.

Default Reject

If no rule matches the incoming click, the traffic is rejected. Always add an "Allow All" rule at the lowest priority to accept unmatched traffic.

Creating a Targeting Rule

Navigate to your campaign, open the Targeting Rules tab, and click Add Rule.

Give the rule a descriptive name (e.g. "Block Low-Quality GEOs").
Add one or more conditions using the condition builder.
Select the action to take when the rule matches.
Set the rule priority.
Save the rule.

Multiple Conditions

All conditions within a single rule use AND logic — every condition must match for the rule to trigger. To implement OR logic, create separate rules with the same action.

Available Conditions

Each condition targets a specific attribute of the incoming click. Supported operators depend on the parameter type (equals, not equals, contains, in list, etc.).

Parameter	Description
Country	Match by 2-letter country code (e.g. US, GB)
State / Region	Match by state or region within a country
City	Match by city name
Browser	Match by browser (Chrome, Firefox, Safari, etc.)
Device Type	Desktop, Mobile, or Tablet
Operating System	Windows, macOS, Android, iOS, Linux, etc.
OS Version	Match a specific OS version or range
Device Brand	Samsung, Apple, Huawei, etc.
ISP	Internet Service Provider name
User Language	Browser language (en-US, fr-FR, etc.)
Traffic Source	The source parameter passed in the tracking URL
Referrer	Referring domain of the click
Sub Affiliate ID	Value of the sub1–sub6 tracking parameters

Rule Actions

When a rule matches, one of three actions is applied:

Action	Behaviour
Allow	Traffic is accepted and forwarded to the campaign landing page.
Fallback	Traffic is redirected to the campaign's configured fallback URL or campaign.
Reject	Traffic is blocked. The click is recorded but the user is not redirected.

Rule Priority

Priority determines the order in which rules are evaluated. Rules with a lower priority number are checked first.

Priority	Evaluated
1	First
2	Second
…	…
99	Last (use for "catch-all" Allow rules)

Tip

Place your most specific rules at high priority (low number) and a general "Allow All" rule at the lowest priority to catch remaining traffic.

Common Rule Examples

Allow US traffic only

Priority	1
Condition	Country equals US
Action	Allow

Priority	99
Condition	(none — catch-all)
Action	Reject

Redirect mobile traffic to a fallback

Priority	1
Condition	Device Type equals Mobile
Action	Fallback

Priority	99
Condition	(none — catch-all)
Action	Allow

Rate this article

★★★★★

Thanks for rating!

Was this article helpful?