Macros and placeholders
Where each Tracker macro format is valid, and which tokens Axalot accepts in offer links and postback templates.
What macros are
Macros are tokens replaced by a platform, partner, or Axalot at runtime. They move IDs and attributes through the tracking flow.
Traffic Source macros
Ad platform values inserted into campaign URLs.
Outgoing templates
Axalot values sent to offer links, HTTP GET callbacks, and Telegram messages.
Affiliate postback mapping
Partner values received by Axalot on incoming conversion URLs.
Push macros
Dynamic values inserted into push notification text.
Console path
Console / Tracker / SourcesConsole / Tracker / Affiliate NetworksConsole / Tracker / Offer LinksConsole / Tracker / PostbacksConsole / Tracker / Push Notifications
Common rule
Use the macro format for the exact place where it is rendered. A token that is valid in one place is not automatically valid anywhere else.
| Place | Replaced by |
|---|---|
| Traffic Source value | Ad platform or traffic network. |
| Offer Link URL | Axalot before sending the click to the destination. |
| Postbacks HTTP GET URL | Axalot when sending an outgoing callback. |
| Postbacks Telegram message | Axalot when sending the message template. |
| Affiliate Network postback mapping | Partner network when sending an incoming conversion postback. |
| Push text macro | Axalot when rendering push content. |
Direction matters
A macro used in an ad platform URL is not automatically valid in an offer URL or postback. Each side has its own replacement rules.
Traffic Source values
Traffic Source values are copied into the campaign entry URL. Put ad-platform macros in the value, not in the query key.
https://track.example/TRACK_ID?creative_id={ad.id}&sub1={placement}Axalot reads only supported campaign-entry parameter names. fbp, fbc, and click_id are not campaign-entry inputs.
Outgoing Tracker macros
Offer Link URLs and /console/tracker/postbacks templates use the same single-brace format. Only these tokens are allowed:
{click_id}
{device_class}
{phone_os}
{is_bot}
{currency}
{creative_id}
{ad_campaign_id}
{source}
{keyword}
{utm_source}
{utm_medium}
{utm_campaign}
{utm_content}
{utm_term}
{sub1}
{sub2}
{sub3}
{sub4}
{sub5}
{sub6}
{sub7}
{sub8}
{sub9}
{sub10}These tokens can be used in:
| Console field | Example |
|---|---|
| Offer Link URL | https://partner.example/signup?cid={click_id}&sub1={sub1} |
| Postbacks HTTP GET URL | https://example.com/pb?cid={click_id}¤cy={currency} |
| Postbacks Telegram Message Template | <b>{click_id}</b> {sub1} {currency} |
Unsupported {...} tokens are rejected. Do not use {event.*}, {campaign.name}, {offer.name}, {fbp}, {fbc}, {cost}, or {{macro}} here.
URL template rules
URL templates must be valid external http:// or https:// URLs. Query keys may be any valid URI-safe partner key, but query values may contain only URI-safe text and the allowed Axalot macros.
https://partner.example/signup?clickid={click_id}
https://partner.example/signup?cid={click_id}&campaign={ad_campaign_id}Affiliate Network postback mapping
Affiliate Network settings describe what the partner sends back to Axalot on incoming conversion URLs: click id, status, revenue, currency, and external id. Those mappings are not the same as Offer Link or Postbacks outgoing templates.