Trackdesk offers four settings that control how conversions are attributed to affiliate clicks: attribution type, attribution priority, cookie expiration, and attribution expiration. They're configured under Settings → Tracking → Conversion attribution.
Attribution type
When a visitor clicks tracking links from multiple affiliates before converting, attribution type decides which click counts:
First touch: the affiliate whose link was clicked first is credited.
Last touch: the affiliate whose link was clicked most recently is credited.
Attribution priority
When a conversion arrives with both a CID/External CID and a coupon code that maps to a different source, attribution priority decides which one wins:
CID priority: the click is the primary source; the coupon is used only as a fallback when the CID can't be resolved.
Coupon priority: the coupon code wins; the CID is only used as a fallback when no recognized coupon code is present.
If only one of the two is present, the setting has no effect; the conversion is attributed to whichever source is available. CID and External CID are treated as the same kind of source for this setting.
Cookie expiration
Cookie expiration controls how long the tracking cookie is saved in a visitor's browser. The cookie holds the information needed to attribute later activity back to the affiliate's click. When the cookie expires, the browser deletes it and no longer carries that attribution context.
Attribution expiration
Attribution expiration is a server-side time limit between a click and the conversion that's tied to it. If the conversion arrives after this window has passed, Trackdesk will reject it, even if the visitor still has a valid tracking cookie or CID.
This setting is optional. If you leave it blank, there is no server-side limit and clicks remain eligible for attribution as long as the cookie or CID is still valid. Set a value in days if you want to cap the click-to-conversion window.
Attribution expiration is configured in the same form as cookie expiration. Whatever value is in effect at the moment of the click determines that click's expiration timestamp. Changing the setting later does not retroactively change clicks already in the system.
Cookie expiration vs attribution expiration
Cookie expiration lives in the visitor's browser. When it lapses, the browser deletes the tracking cookie, so there's nothing to send when a conversion would otherwise fire.
Attribution expiration lives on Trackdesk's side. Even if the CID is still present in the request (for example, when conversions are created via API), Trackdesk refuses to attribute the conversion once this window has passed.
You can set both, set just one, or leave both unset. If both are set, the shorter of the two wins in practice.
Tenant defaults and per-offer overrides
The values on the Conversion attribution page are tenant-wide defaults. Three of the four settings can be overridden on an individual offer's detail page:
Attribution type (first touch vs last touch).
Cookie expiration (in days).
Attribution expiration (in days, or blank for unlimited).
The fourth setting, attribution priority (CID vs coupon code), is tenant-wide only and cannot be overridden per offer.
FAQ
Can I change my cookie length?
Yes. To change the cookie length from the default 30 days to any other value, go to Settings → Tracking → Conversion attribution.
Is there a maximum length for cookie duration?
Yes. The maximum length is 365 days. This limit exists because all major browsers cap cookie lifetimes at 365 days, and setting a higher value results in tracking not working (cookies not saving).
Every change to these settings is recorded in the Activity log along with the previous and new values, so you can see who changed what and when.