Campaigns FAQ
Common Axalot campaign questions about tracking links, streams, filters, rotation, pixels, and live edits.
Console path
Console / Tracker / CampaignsConsole / Tracker / Create CampaignConsole / Tracker / Edit Campaign
Basics
Campaign
The Tracker object that receives traffic and owns the generated tracking link.
Stream
A routing block with filters, pixels, and rotation.
Rotation
One or more weighted destination rows inside a stream.
Traffic Source
The parameter mapping used to build the campaign link and source filters.
When does Axalot generate the campaign link?
Axalot shows the final campaign link after the campaign is saved. The link uses the selected domain, campaign track id, and selected Traffic Source parameter mapping.
If you change the domain or Traffic Source, save the campaign before copying the link again.
Why is my lower stream not receiving traffic?
The most common reason is a broader stream above it.
Check these first:
- A stream without filters is above the lower stream.
- The upper stream has filters that are too broad.
- The lower stream is inactive.
- The lower stream's filters do not match the incoming request.
Should every campaign have a fallback stream?
Usually yes. A fallback stream catches traffic that does not match specific streams.
Use a fallback when paid traffic should always have a known route. Skip fallback only when unmatched traffic should intentionally fail or route to a system destination.
Why can I not disable the last stream?
Axalot requires at least one active stream. A campaign with no active streams cannot route traffic safely.
Why can I not delete the last rotation row?
Each stream must keep at least one rotation item. A stream without rotation has no destination.
Why does every rotation row need an offer link?
The offer link is the final commercial destination for the rotation flow. PWA and Landing rows can add a stage before the offer, but the offer link is still required.
What is the difference between stream filters and Traffic Source parameters?
Traffic Source parameters define which GET parameters are attached to the campaign link and how incoming source values are named.
Stream filters can then use those mapped source fields for routing.
Traffic Source field: creative_id
Campaign URL parameter: creative_id
Stream filter: creative_id IS creative_aWhy does a source-parameter filter not match?
Check the full chain:
- The campaign uses the expected Traffic Source.
- The copied campaign link contains the expected parameter name.
- The ad platform sends a value for that parameter.
- The stream filter uses the mapped field, not a generic query filter.
- The value format is valid for that field.
Can I use several country filters in one stream?
No. Use one country filter and add multiple countries inside it.
Country IS US, CA, GBThe same rule applies to timezone: use one timezone filter with multiple values.
How many filters can a stream have?
A stream can have up to 20 filters.
Keep the filter set smaller when possible. If a stream needs many unrelated filters, split the routing into clearer named streams.
How many pixels can a stream have?
A stream can have up to 5 pixels.
Pixels are selected per stream. Selecting a pixel on one stream does not automatically select it on another stream.
How many rotation rows can a stream have?
A stream can have up to 5 rotation items.
Use one row for stable routing. Use multiple rows only for active destination tests or weighted distribution.
What do rotation weights mean?
Weights control distribution between active rotation items inside the same stream.
Landing A: 50
Landing B: 50This is an even split. A single active item effectively receives all traffic for that stream.
Should I delete or disable a stream?
Disable first when traffic is live or when you may need rollback.
Delete only when the stream is no longer useful for reports, notes, or rollback.
Can one campaign route both PWA and Landing traffic?
Yes. Use separate streams when the audience differs, or separate rotation rows when the audience is the same and you are testing destinations.
Why are my pixel events missing?
Check:
- The click matched the stream where the pixel is selected.
- The pixel is active and available.
- The selected destination generated the expected event.
- The campaign was saved after pixel changes.
What should I check before sending traffic?
- Campaign is active.
- Domain is correct.
- Traffic Source is correct.
- Tracking link includes expected parameters.
- Streams are ordered from specific to broad.
- Fallback is last.
- All active rotation rows have offer links.
- Pixels are selected on the right streams.
- Test click appears in reports with expected stream and source fields.
Live campaign changes
Do not rewrite many filters and destinations in one live edit. Change one thing, save, test, then continue.