Skip to content

Incoming ClickID

Incoming ClickID (External)

Let your traffic source pass its own click id to ShortKit. When conversions are enabled for a link, ShortKit will:

  • Accept an external id via skclick query param on your short link.
  • Use that id as the click id for macro replacement ({clickid}) or for the clid parameter.
  • On conversion, optionally make a server‑to‑server GET request to your partner’s postback URL, replacing {ExternalClickId} with the external id.

Requirements

  • Enabled conversions for the link (toggle in Link settings). This is the only gate — no extra plan flags needed.
  • Optional: a postback URL template set in Link settings.

Step 1 — Pass external id to your short link

Have your traffic source append its unique click id to your short link via skclick:

https://pre.vin/YOUR_SLUG?skclick={external_click_id}

Notes:

  • If skclick is present and non‑empty, it is used as the click id; otherwise, ShortKit generates its own.
  • Allowed values should be reasonably short and URL‑safe. If in doubt, test with alphanumeric/_-.

Step 2 — Place the click id into your destination

You can consume the click id in two ways:

  1. Macro {clickid} inside your target URL (recommended)
Target URL: https://shop.example.com/checkout?cid={clickid}

Result with ?skclick=ABC123: ShortKit replaces {clickid}ABC123 and does NOT append clid.

  1. Auto‑append clid

If there is no {clickid} macro in the target, ShortKit will append ?clid=ABC123 (or &clid= if there are already query params).

Step 3 — Optional S2S postback to your partner

In Link settings, set:

S2S postback for incoming traffic: https://partner.example.com/pb?click={ExternalClickId}

On every conversion for that link, ShortKit will also fire a GET to the postback URL, replacing {ExternalClickId} with the actual click id used for the click (e.g., ABC123).

Example

  1. Share short link with external id:
https://pre.vin/sale?skclick=ABC123
  1. Target uses macro (preferred):
https://shop.example.com/checkout?cid={clickid}
  1. S2S postback template (optional):
https://partner.example.com/conv?ext={ExternalClickId}

On conversion, ShortKit will call:

GET https://partner.example.com/conv?ext=ABC123

Behavior without skclick

  • If skclick is missing or empty, ShortKit generates its own click id and proceeds as usual. No partner postback is performed unless an external id was used.

Testing tips

  • Enable conversions on the link.
  • Click your short link with ?skclick=TEST123.
  • Fire a conversion (via JS SDK or S2S). Check that your partner receives the GET call with TEST123.
  • Try a target with {clickid} and without it to verify both modes.

Related