URL Tokens Reference

Tokens are placeholders in URLs that get replaced at click-time with values from the click record. They look like {token_name} and let you build dynamic URLs that include attribution and visitor context.

Tokens work in three places:

• Lander URLs — destination URLs in Landers.
• Offer URLs — destination URLs in Offers.
• Postback URLs — server-to-server callback URLs in Links → Postback URL.

When a token can't be resolved (the value isn't available for that click), it's replaced with an empty string. The URL still works.

Click Identity​

Time​

UTM Parameters​

Click ID Platforms​

The platform-specific click ID parameter that came in on the URL.

Channel​

Geo (from MaxMind GeoLite2)​

Device​

Network​

Language​

Custom Variables (Source Token Mappings)​

These tokens hold whatever the source's parameter mappings extracted from the incoming URL. See Sources for setup.

Cost / Revenue​

Available in postback URLs (after a conversion fires).

User Agent​

Affiliate Network​

For Offers configured with an affiliate network.

Putting It Together​

Lander URL with personalization​

https://yoursite.com/landing/spring
  ?city={city}
  &country={country_code}
  &source={utm_source}
  &cid={click_id}

A US visitor from LA via Facebook gets:

https://yoursite.com/landing/spring
  ?city=Los%20Angeles
  &country=US
  &source=facebook
  &cid=550e8400-...

Offer URL with affiliate parameters​

https://offer-network.com/track
  ?aff_id=YOUR_AFF_ID
  &offer_id=12345
  &click_id={click_id}
  &sub1={v1}
  &sub2={utm_campaign}

Postback URL forwarding to ad platform​

https://network.com/postback
  ?click_id={external_id}
  &payout={revenue}
  &currency={revenue_currency}
  &transaction_id={click_id}

This forwards external_id (the ad platform's click ID — gclid, fbclid, etc.) and our internal click_id, plus revenue, on every conversion. The ad platform uses external_id to attribute the conversion back to the original ad in their reporting.

URL Encoding​

Token values are URL-encoded automatically. Spaces become %20, special characters get escaped. You don't need to wrap tokens in any encoding helper — just use {token_name} and the value is escaped for you.

Empty / Missing Tokens​

When a token can't be resolved (parameter wasn't in the click URL, geo lookup didn't return a value, etc.), it's replaced with an empty string. The surrounding URL stays valid.

?city={city}&campaign={utm_campaign}

If city is null and utm_campaign is spring:

?city=&campaign=spring

If your destination is sensitive to empty params (e.g. it errors on empty values), use a Lander or Offer with a default in the URL itself, or coordinate with the destination to ignore empties.

Tokens NOT Currently Supported​

These would be useful but aren't in the system yet:

• Conditional tokens ({country_code:US?somevalue:other})
• Concatenated tokens ({utm_source}_{utm_campaign})
• Math/transformations ({cost*100})

Workaround: do these transformations on your destination page or in your postback receiver.

Next Steps​

• Landers — Use tokens in landing page URLs
• Offers — Use tokens in offer URLs
• Sources — Configure Token 1-10 mappings to populate {v1}-{v10}
• Links — Postback URL — Use tokens in conversion postbacks