Campaign examples

Practical Axalot campaign examples for stream order, filters, rotation, pixels, and Traffic Source parameters.

Goal

These examples show campaign structures that map cleanly to the current Axalot Tracker form. Treat them as templates, not fixed rules.

Simple launch

One source, one stream, one destination.

Geo and device split

Different destinations for different traffic segments.

A/B rotation

Same audience, multiple weighted destinations.

Source-parameter routing

Route by campaign, creative, keyword, UTM, or sub values.

Console path

Console / Tracker / Campaigns / Create Campaign
Console / Tracker / Campaigns / Edit Campaign

Example 1: basic offer launch

Use this when the campaign has one audience and one destination.

Campaign
Name: FB US Android CPI - June
Domain: tracking-domain.com
Traffic Source: Facebook
Cost model: CPM

Stream 1: Main
Filters: none
Pixels: Meta primary pixel
Rotation:
  - PWA: App A
    Offer Link: Network A / Offer A
    Weight: 100

Why this works

With no filters, the only stream acts as the campaign route for all incoming traffic. This is fine when there is no split logic yet.

Example 2: mobile and desktop split

Use this when mobile and desktop traffic need different paths.

Stream 1: US mobile
Filters:
  Country IS US
  AND Is Mobile IS yes
Pixels:
  Meta mobile pixel
Rotation:
  - PWA: App A
    Offer Link: Offer A
    Weight: 100

Stream 2: US desktop
Filters:
  Country IS US
  AND Device Type IS desktop
Pixels:
  Meta desktop pixel
Rotation:
  - Landing: Desktop Landing A
    Offer Link: Offer A
    Weight: 100

Stream 3: Fallback
Filters: none
Rotation:
  - Offer Link: Safe fallback offer
    Weight: 100

Order matters

The fallback stream must stay below the filtered streams. If it is moved to the top, it can catch traffic before the mobile and desktop streams are evaluated.

Example 3: landing A/B test

Use this when the audience is the same and only the landing should be tested.

Stream 1: US mobile test
Filters:
  Country IS US
  AND Is Mobile IS yes
Pixels:
  Meta primary pixel
Rotation:
  - Landing: Landing A
    Offer Link: Offer A
    Weight: 50
  - Landing: Landing B
    Offer Link: Offer A
    Weight: 50

Stream 2: Fallback
Filters: none
Rotation:
  - Offer Link: Safe fallback offer
    Weight: 100

Use weighted rotation when the same audience should be distributed across multiple destinations.

Do not use rotation to separate different audiences. Use separate streams and filters for that.

Example 4: creative-based routing

Use this when the Traffic Source sends creative_id and specific creatives need different destinations.

Traffic Source
creative_id parameter: creative_id

Stream 1: Creative A
Filters:
  creative_id IS creative_a
Rotation:
  - Landing: Creative A Landing
    Offer Link: Offer A
    Weight: 100

Stream 2: Creative B
Filters:
  creative_id IS creative_b
Rotation:
  - Landing: Creative B Landing
    Offer Link: Offer A
    Weight: 100

Stream 3: Fallback
Filters: none
Rotation:
  - Landing: Default Landing
    Offer Link: Offer A
    Weight: 100

Make sure the copied campaign link includes the expected parameter name and value from the selected Traffic Source.

Example 5: geo fallback structure

Use this when one campaign receives multiple countries but only some countries have dedicated routes.

Stream 1: Tier 1
Filters:
  Country IS US, CA, GB, AU
Rotation:
  - PWA: Tier 1 PWA
    Offer Link: Tier 1 Offer
    Weight: 100

Stream 2: Europe
Filters:
  Country IS DE, FR, ES, IT
Rotation:
  - Landing: Europe Landing
    Offer Link: Europe Offer
    Weight: 100

Stream 3: Fallback
Filters: none
Rotation:
  - Offer Link: Global fallback offer
    Weight: 100

Use one country filter with multiple countries. Do not add several country filters to one stream.

Example 6: QA-only stream

Use this when a buyer, QA user, or internal network needs a controlled path.

Stream 1: QA
Filters:
  IP IS 203.0.113.10
Rotation:
  - Landing: QA Landing
    Offer Link: QA Offer
    Weight: 100

Stream 2: Production
Filters: none
Rotation:
  - PWA: Production PWA
    Offer Link: Production Offer
    Weight: 100

Do not forget QA streams

Remove or disable QA streams when they are no longer needed. Keep them above production only while testing.

Example 7: platform split

Use this when Android and iOS traffic require different destinations.

Stream 1: Android
Filters:
  Platform IS Android
Rotation:
  - PWA: Android App
    Offer Link: Android Offer
    Weight: 100

Stream 2: iOS
Filters:
  Platform IS iOS
Rotation:
  - Landing: iOS Landing
    Offer Link: iOS Offer
    Weight: 100

Stream 3: Fallback
Filters: none
Rotation:
  - Offer Link: Global fallback offer
    Weight: 100

Setup checklist

Pick the example closest to the real campaign.

Replace names, countries, platforms, source parameters, pixels, and destinations with real records.

Keep specific streams above fallback.

Save and test the generated link with realistic Traffic Source parameter values.

Campaign examples

Simple launch

Geo and device split

A/B rotation

Source-parameter routing

On this page