Redirect tokens: passing click data through to your landing page
How to hand the destination page real values from the click — the click ID, sub-IDs, affiliate, country, device and more — using #token# placeholders, either offer-wide or on a single landing page URL.
Sometimes the destination page needs to know something about the click that sent the visitor there — which affiliate they came from, which traffic source, what country they are in, or the click ID your advertiser will echo back on their conversion pixel. Redirect tokens are how you pass that information along. When a visitor clicks a tracking link, LimeliJourney replaces #token# placeholders with that click's real values before redirecting, so the landing page (or your own funnel) arrives already carrying exactly the fields you chose.
Two places to put tokens
There are two ways to place tokens, and they solve different problems:
- Offer-wide redirect parameters. Enter a query-string template such as
clickid=#click_id#&source=#s1#, and those parameters are appended to every tracking-link redirect for the offer, whichever landing page serves. Use this when every destination should receive the same fields. - Tokens inside a landing page URL. Any landing page URL can carry tokens directly, for example
https://example.com/landing?promo=#s2#. Only that one page passes those values. This is the precise option when different pages need different parameters.
A token legend lets you click any token to insert it, and a live preview shows the final redirect with sample values as you build the template.
What you can pass
The token vocabulary covers the whole click. You can pass the click's own ID (the same value appended as ll_cid), the affiliate, offer, campaign, creative, and contract IDs, any of the five sub-IDs, the resolved affiliate payout, the visitor ID that identifies the same consumer across offers, and enrichment from the click itself — a two-letter #country#, a #device# of mobile, tablet, desktop or bot, and the click #date#. Tokens are case-insensitive, and a value that simply was not present on the click becomes an empty value rather than junk.
A couple of honest limits are worth knowing. Region-level geo is not available — the lookup resolves country only. And advertiser revenue is never exposed on a redirect. Because #payout# places the affiliate payout on a consumer-visible URL, only use it where the destination is yours or the advertiser expects it.
Order and precedence
The final redirect is assembled in a defined order: the landing page URL with its tokens replaced, then your offer-wide redirect parameters with theirs replaced, then LimeliJourney's own ll_cid and ll_vid. If the same parameter name appears twice, the later one wins. A small tip: if you want the click ID on the URL under our own name with no duplication, write ll_cid=#click_id# in your redirect parameters and it merges with the auto-appended one instead of adding a second copy.
The click-ID passthrough toggle
By default every redirect also carries ll_cid and ll_vid, which is the recommended attribution path. You can turn that off per offer — but only do so when you are already passing the click ID yourself via a #click_id# token under whatever parameter name your advertiser expects, and you have wired your conversion pixel to that value. The ll_cid cookie is still set either way, so cookie-based attribution keeps working as a fallback.
Want us to set up token passthrough against your advertiser's exact requirements? Book a demo and we will get the template right with you.