Definition
FBCLID means Facebook Click Identifier. It is a URL parameter that Meta adds after an ad click so the visit can be matched back to the click for attribution and conversion reporting.
Example
Example: a user clicks a Meta ad and lands on `https://example.com/pricing?fbclid=ABC123...`. That parameter tells you the visit came from a specific Meta ad click and may later be used for attribution or conversion matching.
How to use it
- Start with the plain meaning: FBCLID is not campaign naming, and it is not a persistent customer ID. It is a click-level identifier attached to the landing-page URL.
- 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 session still stays readable across GA4, BI, and CRM reports.
- Keep FBCLID for Meta-side matching, but do not treat it as a replacement for UTMs, consent handling, or your own attribution rules.
Measured as
Measure FBCLID: what the URL parameter means and how Meta uses it 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
- If someone asks what FBCLID means, the short answer is simple: it is the click ID Meta appends to a landing-page URL after an ad click.
- If Meta conversions look weak or disappear, check whether redirects, vanity URLs, or cross-domain hops are stripping FBCLID before blaming campaign performance.
- Start with the plain meaning: FBCLID is not campaign naming, and it is not a persistent customer ID. It is a click-level identifier attached to the landing-page URL.
- 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.
Next decision
- Decide whether you need FBCLID only for platform attribution or also for offline conversion uploads and CRM matching, because storage and retention rules depend on that workflow.
- Verify FBCLID, UTMs, consent behavior, and deduplication together before comparing Meta numbers to GA4 or server-side reporting.
- 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.