Skip to main content
A rotator decides which destination a visitor receives. It can keep a simple route to one offer, split traffic between variants, or apply different paths when visitor conditions match. Use a Campaign-only Rotator when the routing belongs to one campaign. Use a shared rotator when several campaigns should use and update the same routing configuration.

​
Understand rules, paths, and destinations

Routing proceeds through three choices:
  1. Rule. Metricanic evaluates enabled conditional rules in order. A usable matching rule takes precedence over Default Paths.
  2. Path. It selects an eligible path in that rule according to its relative weight.
  3. Destination. It selects an offer, plus a landing when the path has landings, using their weights.
Default Paths are the fallback when a conditional rule does not produce a usable route. Keep at least one enabled default path with an enabled offer. The default rule has no conditions and cannot be disabled. A path can use Offers only or Landers & Offers. With landings, the visitor first receives the selected landing and its tracked CTA leads toward the offer. With Offers only, there is no landing step.

​
Use weights to express proportions

Weights are relative within the pool where they appear. They do not have to total 100. Selection is random, so a small test sample will not necessarily match the proportions. Weights do not automatically adjust from conversion or profit results. If a path has multiple landings and offers, Metricanic considers their combinations. A pair’s relative weight is the landing weight multiplied by the offer weight. Two equally weighted landings and two equally weighted offers create four possible pairs, not two fixed pairs. To enforce Landing A → Offer A and Landing B → Offer B, use two paths, each containing its own landing and offer. Then use the path weights to divide traffic.

​
Build a reliable default first

  1. Open Rotators and click Create for a shared rotator. Enter Rotator name and Country. Alternatively, open 3. Rotator in a campaign and choose Campaign-only Rotator.
  2. Under Default Paths, click Add Default Path if needed and select the path.
  3. Enter Path name, choose Path Destination, and select the offer or landings and offers.
  4. Set weights and keep the path and destinations enabled. Weights must be whole numbers from 1 to 1000. Disable an item to remove it from selection rather than assigning zero.
  5. Save, attach the shared rotator to the campaign if needed, and test the route.
A rule supports up to 10 paths. Each path needs an enabled offer, including paths you keep disabled for later use. Asset countries must be compatible with the campaign and rotator.

​
Add a conditional route

Suppose mobile visitors need a shorter landing while everyone else can use the standard page. Click Add Rule under Rule-based Paths. Select the rule, add a Device Type condition with the appropriate mobile value, and configure its path with the short landing and an offer. Keep the standard landing in Default Paths. Conditions within a rule must all match. Available fields include geography, language, device, operating system, browser, network context, referrer, visit cost, External ID, and captured tokens. Choose operators appropriate to the field, such as is, in list, or a numeric comparison. Order specific rules before broader ones. If a broad mobile rule already routes the visitor, a later rule for a particular mobile country will not take over. Use the reorder controls to express the intended precedence. Some request context can be unavailable. Keep a usable default route instead of assuming every visit has every device, network, or referrer field.

​
Reuse or copy safely

In a campaign, Use existing rotator attaches a shared rotator. Edit shared rotator changes it for every attached campaign. Use Copy to campaign-only rotator when you want the current shared rules as an independent starting point. Switching directly to Campaign-only Rotator starts a blank configuration unless the campaign already has its own private rotator. A shared rotator must be Global or match the campaign country. A Global campaign requires a Global shared rotator. Country selection controls compatibility. A Country condition controls routing by the detected visitor country.

​
Verify both the special route and fallback

Test one visit matching the condition and another that should use Default Paths. Check the selected destination and review the path, landing, and offer breakdowns in the campaign report. For Direct Script Mode, the visitor has already opened a page. Only paths containing that configured page can serve its visit. Changing landing weights cannot move that browser to another arrival page. Read tracking modes before applying a redirect split-test design to direct traffic. If saving fails, check for missing offers, invalid weights, or an unusable default. If the wrong route wins, check rule order, actual captured condition values, and which paths remain enabled.