Skip to main content

Landers

A Lander is a reusable landing-page config. Define one lander once — its URL, weight, country/language targeting — and you can drop it into multiple links' paths. Useful when you have a small set of landing pages but many campaigns pointing at them.

Video Walkthrough

Watch: Landers and Offers — 0:00–5:00 (video coming soon)

When to Use a Lander vs a Direct URL​

Use a Direct URL in a path when:

  • The destination is one-off, not reused elsewhere.
  • You don't need to share the same URL across many links.

Use a Lander when:

  • The same landing page appears in many links.
  • You want to manage country/language targeting in one place.
  • You want to enable/disable the destination across all links at once (toggle a lander off → it stops being picked everywhere).

Lander Fields​

Open Click Tracking → Landers → New Lander (or click an existing lander to edit).

Name​

Human-readable label for this lander. Shows up in lander pickers, reports, and tooltips.

Example: Spring Promo — Hero v3

URL​

The actual URL the visitor lands on. Can include URL tokens that get replaced at click-time with values from the click record.

Example:

https://yoursite.com/landing/spring?city={city}&utm_source={utm_source}

When a visitor from Los Angeles clicks via a Facebook ad, this becomes:

https://yoursite.com/landing/spring?city=Los%20Angeles&utm_source=facebook

See URL Tokens Reference for every available token.

Language​

ISO language code (e.g. en, es, fr, de). Optional. Used for filtering — when a lander is added to a link, the system can prefer landers whose language matches the visitor's accept-language header.

Leave blank for language-agnostic landers.

Country​

ISO country code (e.g. US, GB, BR). Optional. Same logic as language — used for matching landers to visitors by geo.

Leave blank for country-agnostic landers.

Group​

Optional category for organizing landers. Free-form text. Shows up as a filter in the Landers list.

Example: Q1 Campaigns, Affiliate Promo, Black Friday.

Tags​

Optional keyword tags. Multiple per lander. For cross-cutting filters that don't fit Group.

Weight​

Default weight when this lander is added to a link's path. Higher weight = picked more often relative to other landers/offers in the same path.

When you add the lander to a link, you can override this per-link. The lander's own weight is the default starting value.

Enabled​

When OFF, this lander is skipped everywhere — even in links that have it configured. Useful for temporarily pausing a destination without removing it from every link manually.

Notes​

Free-form internal notes. Doesn't affect anything functional.

URL Tokens​

The URL field supports placeholder tokens that get replaced at redirect-time with click data. Tokens are wrapped in curly braces:

https://yoursite.com/?city={city}&campaign={utm_campaign}&id={click_id}

Common Tokens​

TokenReplaced With
{click_id}The unique UUID for this click
{utm_source} / {utm_medium} / {utm_campaign} / etc.The matching UTM parameter from the visitor's URL
{country_code} / {country_name} / {city} / {region_name}Geo-IP enriched fields
{device_type} / {os_name} / {browser_name}Device-detection fields
{external_id}Your custom external tracking ID
{v1} through {v10}Custom variables mapped via Sources
{date}Current date (YYYY-MM-DD)

See URL Tokens Reference for the full list.

Tokens that Don't Have a Value​

If a token can't be resolved (e.g. {utm_source} but the visitor's URL had no utm_source), it's replaced with an empty string. The URL still works — the placeholder just disappears.

In a link's edit page, on a path:

  1. Click Add Landing Page in the path's URL list.
  2. Pick the lander from the dropdown.
  3. The lander's URL fills in automatically. You can override the per-link weight if you want this link to weight it differently.

The same lander can be added to as many links as you want. Editing the lander's URL updates everywhere that lander is used.

Worked Example: Three Country Landers​

Goal: maintain three landing pages — US, UK, Germany — and assemble different links from them without duplicating URLs.

Step 1: Create three landers.

NameURLCountryWeight
Spring — UShttps://you.com/spring-us?city={city}US1
Spring — UKhttps://you.com/spring-uk?city={city}GB1
Spring — DEhttps://you.com/spring-de?city={city}DE1

Step 2: Use them in a link.

Create a link "Spring Promo — Geo". Add all three landers to a single path. Set Distribution Type to Geo, then add rules:

  • Rule priority 10: country_code is US → use Lander "Spring — US"
  • Rule priority 9: country_code is GB → use Lander "Spring — UK"
  • Rule priority 8: country_code is DE → use Lander "Spring — DE"
  • Default path: any lander as fallback

Step 3: Reuse the landers in another link for a different campaign. Same destinations, no duplicate URL maintenance.

When you later update the URL for "Spring — US" (say, to fix a typo), it updates everywhere the lander is used.

Next Steps​