Tracker overview
The core Tracker map in Axalot: campaigns, sources, domains, flows, offers, postbacks, pixels, landings, PWA, and push.
What Tracker controls
Tracker is the Axalot workspace for routing paid traffic, building campaign links, storing click metadata, and connecting later events back to the original click.
Campaigns
The launch unit: domain, traffic source, cost model, push group, streams, and generated tracking link.
Sources
Reusable traffic source profiles with GET parameter names and platform macro values.
Offers and links
Affiliate networks, offers, and destination URLs used inside campaign rotations.
Events
Postbacks, pixels, Telegram, and HTTP callbacks used to receive or send conversion signals.
Direction matters
In Axalot docs, postback means an incoming conversion signal from a partner network into Tracker. Pixel means an outgoing event from Tracker to Facebook, HTTP GET, or Telegram.
Main flow
Create the supporting records: domain, Traffic Source, affiliate network, offer, and offer link.
Create a campaign and select the domain and Traffic Source.
Configure streams: filters decide which traffic enters a stream, rotation decides where accepted traffic goes.
Copy the generated campaign link into the ad platform.
Receive partner events through postbacks and send optimization events through pixels when needed.
Console sections
Console / Tracker / CampaignsConsole / Tracker / SourcesConsole / Tracker / DomainsConsole / Tracker / Affiliate NetworksConsole / Tracker / OffersConsole / Tracker / Offer LinksConsole / Tracker / PostbacksConsole / Tracker / ReportsConsole / Tracker / PWAConsole / Tracker / LandingsConsole / Tracker / Push Notifications
Entity map
| Entity | Purpose | Connects to |
|---|---|---|
| Campaign | Main tracking configuration and generated click URL | Domain, Traffic Source, streams, push group |
| Domain | Public tracking host used in the campaign link | Campaign |
| Traffic Source | URL parameter and macro mapping for an ad platform | Campaign |
| Stream | Rule block inside a campaign | Filters, rotation destinations |
| Filter | Condition used to route or reject traffic | Stream |
| Rotation | Weighted destination list inside a stream | Offer links, landings, PWA |
| Affiliate Network | Partner network configuration and URL/postback macro defaults | Offers, offer links |
| Offer | Commercial offer or product being promoted | Affiliate network, offer links |
| Offer Link | Final destination URL or flow endpoint | Campaign stream rotation |
| Postback | Incoming conversion signal | Click id, status, revenue, currency |
| Pixel | Outgoing event destination | Facebook, HTTP GET, Telegram Bot |
| Landing | Hosted intermediate page | Campaign stream rotation |
| PWA | Store-like app flow | Campaign stream rotation |
| Push Group | Push notification setup selected by campaign | Campaign |
Campaign link contract
The campaign link is built from the selected domain, campaign track id, and selected Traffic Source values.
https://tracking-domain.com/TRACK_ID?click_id={clickid}&campaign_id={campaign.id}The source controls query parameters. The campaign controls where traffic goes after the click is accepted.
Incoming vs outgoing events
Incoming events are postbacks from partner networks. They usually carry click_id, status, revenue, and currency.
Use them to update campaign statistics after a registration, deposit, purchase, or rejected conversion.
Outgoing events are pixels or callbacks sent from Axalot to another service. Current postback types in Tracker are Facebook, HTTP GET, and Telegram Bot.
Use them when a traffic source or team channel must receive conversion events.
Build order
Use this order when documenting or setting up a new Tracker workspace:
- Domains
- Traffic Sources
- Affiliate Networks
- Offers
- Offer Links
- Campaigns
- Streams and filters
- Postbacks
- Pixels and callbacks
- Reports