<b>Click ID pass-through — tracing the token end to end</b>

<b>Click ID pass-through — tracing the token end to end</b>

If the click ID doesn't survive the full chain, your postback can't match the conversion and it shows as anonymous. Trace it deliberately.

The chain to verify:

— Traffic source generates click ID → passes into your tracker's incoming parameter
— Your tracker stores it and injects it into the offer URL token (<code>{clickid}</code> / <code>{subid}</code>)
— Offer carries it through any advertiser-side redirect
— Advertiser returns it in the postback → tracker matches it to the original click

How to test:

— Append a known sentinel value (e.g. <code>QA_TEST_001</code>) as the click ID and follow it visually at each URL
— Confirm the value isn't truncated — some sources cap subid length at 32 or 50 chars
— Confirm no URL-encoding corruption: a click ID with special chars must be encoded once, not double-encoded
— Watch for parameter name collisions: source <code>subid</code> vs offer <code>sub_id</code> vs network <code>aff_sub</code>

Document the exact token name at each hop in a 4-row table per offer.

Save this SOP. Run this before every launch.