This guide explains how to use click ID placeholders in your destination URL (the URL where visitors are sent after they click your Qliker tracking link or rotator). You type the placeholders exactly as shown, including the square brackets.
What are placeholders?
Placeholders are short codes in the destination URL. When a visitor clicks, Qliker replaces each code with a number before the visitor is redirected.
You do not need to know how the numbers are generated; use them wherever your advertiser, network, or your own tracker expects a click or conversion ID in the link.
[clickid] — this click
Meaning: Identifies this specific click (the visit that just happened).
Typical use: Passing the current click ID to an offer page, affiliate network, or your own “thank you” page so you can match it with conversions or postbacks.
Availability: Supported on tracking links (link flows that use the link redirect logic). It refers to the click created for that link open.
[fclickid] — first recorded click
Meaning: Identifies the visitor’s first click that Qliker stored for that browser in this context. Later clicks can still send that same first-click value in the URL when you use [fclickid].
Typical use: Attribution models where you want later steps (extra links, funnels, rotators) to still reference the original entry click, not only the latest one.
Important:
If there is no stored “first click” for that visitor, [fclickid] may be left unchanged in the URL (you might still see the text [fclickid]). Test your funnel from a fresh browser (or incognito) starting from the link that should create the first click.
On rotators, [fclickid] is only filled when that first-click information already exists (for example after the visitor previously clicked a tracking link that set it). Rotators alone may not create the “first click” record the same way links do.
How to add them to your URL
Put the placeholders anywhere in the destination URL — in the path or in query parameters — as your partner’s documentation requires.
Examples:
https://example.com/offer?cid=[clickid]
https://example.com/go?first=[fclickid]&last=[clickid]
https://example.com/promo/[clickid]/landing
Use only the exact spellings: [clickid] and [fclickid] (lowercase, with brackets).
Using click IDs with your postback URL
A postback URL (server-to-server / S2S) is what the affiliate network calls when a conversion happens. It should carry the same click reference you sent on the click, so Qliker can tie conversion → click.
There are two steps: send the ID out on the offer link, then send it back on the postback using the network’s own dynamic tokens.
Step 1 — Offer / destination URL (store the ID on the network)
Add a sub-ID (or similar) parameter using a Qliker placeholder. Networks use different names (sub1, subid, clickid, cid, etc.) — use their documentation.
Examples:
https://affiliatenetwork.com/offer/123?sub1=[clickid]
https://affiliatenetwork.com/offer/123?sub1=[fclickid]
(only if [fclickid] is correct for your funnel; see section 3.)
After the click, the visitor lands on the offer with numbers instead of the placeholders, and the network stores that value.
Step 2 — Postback URL on the network (return the ID to Qliker)
Set the postback URL to Qliker’s sales endpoint for your account.
Base URL (example account username johndoe):
https://johndoe.qltrk.com/t/post/sales
Append parameters like any URL:
First query field: ?name=value
Additional fields: &name=value
Networks use their macro syntax for values they inject ({sub1}, {transaction_id}, etc.). Those macros go on the postback URL you paste into the network — not inside Qliker’s square-bracket placeholders (which are only for your destination URL in Qliker).
Illustrative pattern (macros are examples; replace with your network’s real tokens and with the full string from Qliker):
https://johndoe.qltrk.com/t/post/sales?u=YOUR_USER_ID&ref=YOUR_REF&…&s1={sub1}
Here {sub1} would stand for whatever the network sends back for the same field you used in step 1 (e.g. what you passed as sub1=[clickid]).
Important: The complete postback URL (correct u=, ref=, click parameter such as s1, and network-specific fields) is normally generated or copied from Qliker’s Postback Builder in your dashboard. The path /t/post/sales alone is not enough; the full URL with all required query parameters must match Qliker’s instructions for your integration.
Tips
Test end-to-end with a new incognito window so you see the same experience as a new visitor.
If [fclickid] appears literally in the final URL, check that the visitor first hit a flow that records the first click (usually a tracking link), then continue the journey.
Match parameter names (cid, click_id, etc.) to what your network or landing page expects; Qliker only substitutes the values for [clickid] and [fclickid].
Privacy (short)
“First click” behavior relies on storing that first click identifier in the visitor’s browser (and related server-side rules) so later pages can reuse it. Use your own privacy policy and cookie notices as required for your visitors and regions.