A unique identifier the ad platform appends to your landing URL at click time — gclid, fbclid, ttclid — stored first-party and matched when a conversion later fires, joining outcome to click.

Why do click IDs matter for CAPI?

Server-side events carrying the stored click ID match with high confidence — Meta's fbc parameter and Google's enhanced conversions both lean on it — while events without it fall back to weaker matching.

What breaks click ID tracking?

Redirects that strip query parameters, single-page apps mishandling the landing URL, shortened first-party cookie lifetimes, and site migrations — test with a live ad click after every change.

Growth Marketing Glossary

Click ID

click I·Dnoun

The click's serial number — a token in the URL that lets Tuesday's click claim Friday's conversion.

Schematic — the identifier riding the landing URL

Term: Click ID
Examples: gclid (Google), fbclid (Meta), ttclid
Rides: The landing-page URL as a parameter
Enables: Click-to-conversion matching, CAPI joins

Forms & parts of speech

click ID · noun

The click's URL token.

"Store the click ID at landing and send it back with the CAPI event - that's the join key."

Definition in plain terms

A click ID is a unique identifier the ad platform appends to your landing-page URL at the moment of the click — Google's gclid, Meta's fbclid, TikTok's ttclid, Microsoft's msclkid. It is the click's serial number: when a conversion later fires with that identifier attached (via cookie, or passed back server-side), the platform matches outcome to click with certainty, powering CLICK-THROUGH ATTRIBUTION without guesswork. Small string, central plumbing.

The mechanics

The flow: the user clicks, the platform decorates the destination URL (?gclid=...), and the site's tags typically store the value in a first-party cookie scoped to your domain. When a conversion event fires, the stored ID rides along, and the platform joins event to click — Google's auto-tagging plus conversion tag is exactly this loop, with the gclid additionally carrying campaign context into Google Analytics without manual UTM-PARAMETERS. The privacy era raised the click ID's status from convenience to load-bearing. As third-party cookies died, the first-party-stored click ID became the durable join key — CONVERSIONS API implementations send it with server-side events (fbc for Meta's stored fbclid, gclid in enhanced conversions uploads), and match quality rises materially when it is present. The operational gotchas are mundane and expensive: redirects and URL rewrites that strip query parameters silently amputate attribution; single-page apps that mishandle the landing URL lose the token; cookie lifetimes cap the attribution memory (Safari's ITP truncates first-party cookie lifespans, shortening the window the stored ID survives); and case-sensitive servers occasionally choke on decorated URLs. The audit is simple — click a live ad, confirm the parameter lands, confirm the cookie sets, confirm the conversion payload carries it.

When it matters

Click IDs matter to anyone running platform conversion tracking, and matter doubly in server-side setups, where the stored ID is the difference between high-confidence matching and modeled approximation. They matter most at infrastructure changes — replatforms, redirect cleanups, SPA migrations, consent implementations — each historically capable of stripping the parameter and quietly blinding attribution. The discipline is plumbing verification: preserve query strings through every redirect, store the IDs first-party at landing, pass them with server events, and test the loop end to end after every site change.

Worked example. An outdoor-gear retailer migrates to a new storefront and Google Ads conversions fall 35% while revenue holds. The culprit is a 'clean URLs' redirect rule the new platform shipped by default - it strips query parameters, so every gclid dies at the front door, no first-party cookie gets set, and conversions can no longer join their clicks; Smart Bidding, starved of matched signal, starts misallocating budget. The fix takes a morning once found: redirects preserve query strings, the tag stores gclid and fbclid at landing, and the CAPI feed attaches the stored IDs to server events. Match rates recover, reported conversions snap back within the click window, and the team adds a one-line check to its deployment list - click a live ad, watch the parameter survive. The campaign had never stopped working; its serial numbers had stopped arriving.

Failure modes to watch. Redirect and URL-rewrite rules that strip query parameters and amputate attribution; SPAs that lose the landing URL before tags read it; server-side events sent without the stored click ID, downgrading matches to approximation; ignoring cookie-lifetime truncation when judging attribution windows; and never testing the loop with a real ad click after site changes.

Synonyms & antonyms

Synonyms

click IDgclidclick identifier

Antonyms

organic visituntagged traffic

Origin & history

Click identifiers arrived with Google's auto-tagging — the gclid let AdWords and Analytics join click to session without manual tagging — and multiplied across platforms (fbclid appearing in 2018 as Meta's equivalent). The privacy era promoted them from convenience to join key, as first-party-stored click IDs became the matching spine of server-side conversion tracking.

Etymology: source.

Usage trends

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Common questions

What is a click ID?: A unique identifier the ad platform appends to your landing URL at click time — gclid, fbclid, ttclid — stored first-party and matched when a conversion later fires, joining outcome to click.
Why do click IDs matter for CAPI?: Server-side events carrying the stored click ID match with high confidence — Meta's fbc parameter and Google's enhanced conversions both lean on it — while events without it fall back to weaker matching.
What breaks click ID tracking?: Redirects that strip query parameters, single-page apps mishandling the landing URL, shortened first-party cookie lifetimes, and site migrations — test with a live ad click after every change.

Related tools & calculators

toolCAC calculator
toolLTV:CAC calculator

Resources & people to follow

referenceGoogle Ads — auto-tagging and the gclid
referenceMeta developers — fbp/fbc parameters for the Conversions API
referenceRGM analysis — click a live ad after every deploy; attribution dies of stripped query strings, not strategy

Curated, non-competitor resources verified per term.

Related training

modulePerformance marketing

Disciplines

Areas of marketing where click id is a core concern:

Performance marketingGrowth strategy

Sources

trendsGoogle Trends — "gclid"