Redirect-Based Conversion 

Track Conversions Even When you Don’t Control the Landing Page

Use redirect URLs to pass and capture CIDs — then trigger affiliate conversions via postback, even on external or third-party landing pages.

Start 14-day FREE trial
No Credit Card Required

Trackdesk customer logo — a Trackdesk affiliate program tracking customer.
Case Study
Trackdesk customer logo — a Trackdesk affiliate program tracking customer.
Trackdesk customer logo — a Trackdesk affiliate program tracking customer.
Case Study
Trackdesk customer logo — a Trackdesk affiliate program tracking customer.
Case Study
Trackdesk customer logo — a Trackdesk affiliate program tracking customer.
Trackdesk customer logo — a Trackdesk affiliate program tracking customer.
Case Study
Trackdesk customer logo — a Trackdesk affiliate program tracking customer.
Case Study
Trackdesk customer logo — a Trackdesk affiliate program tracking customer.
Trackdesk customer logo — a Trackdesk affiliate program tracking customer.

Keep Campaign Context Across the Redirect

When affiliates add their own parameters to a tracking link, like UTM tags or ad click IDs, Trackdesk can pass them on to the advertiser's landing page. That way, campaign data doesn't get lost in the redirect.

  • Nothing gets overwritten. If the landing page URL already has a parameter with the same name, Trackdesk keeps the original value.

  • Trackdesk's own tracking parameters aren't passed on. This includes affS1–affS5, target, deepLink, and redirect.

  • Anchor links keep working. Any #section part of the landing page URL stays as is.

How to enable: The setting is off by default. Go to Settings → Redirect tracking → Forward query parameters, turn on "Forward non-conflicting query parameters to the landing page?", and save. You'll need Redirect Tracking on your plan and permission to change tracking settings.

Frequently Asked Questions

When a user clicks an affiliate link, Trackdesk adds a unique CID (click ID) to the landing page URL. You capture that CID on your side (e.g., using cookies or local storage) and use it to fire a postback once the user converts. The CID ensures proper attribution, even if the final conversion happens on a different domain.