Definition
FBCLID is Meta's click identifier added to landing page URLs after an ad click. It helps match sessions and conversions back to Meta ads, so losing it can break attribution and conversion reporting.
Example
A landing page URL includes ?fbclid=... after a Meta ad click so the visit can be matched to a later conversion event.
How to use it
- Keep the full query string intact across redirects, vanity URLs, and cross-domain hops.
- Use clean UTMs alongside FBCLID so reports stay readable outside Meta.
- If you send both pixel and server events, use deduplication so matching does not double-count conversions.
- Store FBCLID only as long as your attribution and consent policy requires.
Common mistakes
- Stripping FBCLID during redirect chains and then blaming Meta for missing conversions.
- Using FBCLID without consistent UTMs, which makes cross-channel reporting hard to trust.
- Treating FBCLID like a durable user identifier instead of a click-level attribution signal.
- Comparing Meta numbers to GA4 without aligning attribution windows and deduplication rules.
Compare it with
- FBCLID is a Meta-generated click identifier. UTM parameters are campaign tags you control so the visit still stays readable across GA4, BI, and CRM reports.
- Keep FBCLID for platform-side matching, but do not treat it as a replacement for UTMs, consent handling, or your own attribution rules.
Measured as
Measure FBCLID: what it is, when it appears, and why it matters with a fixed attribution window, conversion event, and spend basis before comparing campaigns or creative tests.
Misused when
- Stripping FBCLID during redirect chains and then blaming Meta for missing conversions.
- Using FBCLID without consistent UTMs, which makes cross-channel reporting hard to trust.
- Treating FBCLID like a durable user identifier instead of a click-level attribution signal.
- Comparing Meta numbers to GA4 without aligning attribution windows and deduplication rules.
Operator takeaway
- Keep the full query string intact across redirects, vanity URLs, and cross-domain hops.
- Use clean UTMs alongside FBCLID so reports stay readable outside Meta.
- If you send both pixel and server events, use deduplication so matching does not double-count conversions.
- Use FBCLID: what it is, when it appears, and why it matters only inside a stable attribution rule, conversion definition, and time window so campaign comparisons stay honest.
- If performance changes, check whether the metric moved for a real business reason or because the measurement setup changed underneath you.
Next decision
- Quantify the impact with Incrementality Lift Calculator if you need to turn the definition into an operating assumption.
- Read UTM + GA4 attribution: practical tracking for paid ads (without lying to yourself) if the decision depends on interpretation, policy, or trade-offs beyond the raw formula.
Where to use this on MetricKit
Calculators
- Incrementality Lift Calculator: Estimate incremental conversions, incremental ROAS, and incremental profit from a holdout test.
Guides
- UTM + GA4 attribution: practical tracking for paid ads (without lying to yourself): A practical guide to UTMs and GA4: consistent source/medium/campaign tagging, conversion deduplication, and common attribution traps.
- Attribution vs incrementality: what to trust, when, and how to test: A practical guide to attribution vs incrementality: common attribution models, window pitfalls, how MER/marginal ROAS fit in, and how to run holdout/geo tests.