Landings

Console path

Console / Tracker / Landings
Console / Tracker / Campaigns / Streams / Rotation

How landings are used

Landings can be selected as pre-landings or main landing destinations in campaign rotation. Use them when traffic should see a page before reaching the offer link.

Common patterns

Pattern	Use when
Pre-landing -> Offer	The first page qualifies or warms the visitor.
Landing -> Offer	The landing is the main destination before the offer.
Pre-landing -> Landing -> Offer	The flow needs two page stages.

Landing placeholders

Hosted landing HTML can print click and source values with double braces:

Click: {{click_id}}
Source: {{utm_source}}
Placement: {{sub1}}
Next step: {{next_url}}

Use {{sub1}}, not {sub1}. Single-brace values are not replaced inside landing HTML.

Available values

Placeholder	Value
`{{click_id}}`	Axalot click id for the current visitor.
`{{next_url}}`	URL for the next step in the flow.
`{{fb_pixel_1}}`-`{{fb_pixel_5}}`	Facebook pixel ids assigned to the route.
`{{tiktok_pixel_1}}`-`{{tiktok_pixel_5}}`	TikTok pixel ids assigned to the route.
`{{country}}`	Visitor country.
`{{region}}`	Visitor region.
`{{city}}`	Visitor city.
`{{platform}}`	Visitor platform.
`{{device_type}}`	Visitor device type.
`{{timezone}}`	Visitor timezone.
`{{accept_language}}`	Visitor `Accept-Language` header.
`{{ext_click_id}}`	External click id from the traffic source.
`{{currency}}`	Click cost currency in ISO 4217 format, for example `USD`, `EUR`, or `TRY`.
`{{creative_id}}`	Creative id from the traffic source.
`{{ad_campaign_id}}`	Ad campaign id from the traffic source.
`{{source}}`	Source value from the traffic source.
`{{keyword}}`	Keyword value from the traffic source.
`{{sub1}}`-`{{sub10}}`	Custom source values from the campaign-entry URL.
`{{utm_source}}`	UTM source.
`{{utm_medium}}`	UTM medium.
`{{utm_campaign}}`	UTM campaign.
`{{utm_term}}`	UTM term.
`{{utm_content}}`	UTM content.

Values are HTML-escaped before rendering. Empty, too long, or invalid text is rendered as an empty string.

PWA request context

When a campaign opens PWA Core, /config.json also receives tracker device context from the current request:

{
  "tracker_context": {
    "device_class": "mobile",
    "phone_os": "android",
    "is_bot": "false"
  }
}

PWA Core stores this payload for runtime use. It does not append these values to offer URLs by itself.

For partner offer URLs, insert the matching single-brace macros only when the partner needs them:

https://partner.example/start?cid={click_id}&device={device_class}&os={phone_os}&bot={is_bot}

Allowed values are mobile, desktop, tablet, unknown for {device_class}; android, ios, other, unknown for {phone_os}; and true, false, unknown for {is_bot}.