Conversion tracking with short links, end to end

The click identifier

When conversion tracking is on, the redirect appends a unique click identifier to the destination URL. That identifier is the thread linking the click to whatever happens next.

Capture it on arrival

On the landing page, read the identifier from the query string and store it — a first-party cookie, session storage, or a hidden form field. Do this on the first page view, before any client-side routing rewrites the URL and drops the parameter.

Report the conversion

When the visitor does the thing that matters, send the identifier back with a value. A server-side call is the reliable option: it survives ad blockers, cannot be spoofed from the page, and works for conversions that happen later, like a subscription that activates after a trial.

The pixel option

For teams without backend access, a one-pixel image on the thank-you page carrying the identifier works. It is easier to deploy and easier to block, so expect it to undercount.

Attribution reality

This is last-click attribution at the link level. It answers "which link produced this conversion", not "which touchpoint deserves the credit". That is usually the right question for campaign links, but do not let it stand in for a full attribution model.

What to watch for

Duplicate reports when a thank-you page is refreshed — deduplicate on the identifier. Missing identifiers when the destination strips query parameters. And a conversion count that is suspiciously round, which usually means someone is firing the pixel on page load rather than on the actual event.