Skip to content
Glossary · Tracking

fbclid

Facebook Click Identifier

How it works

When someone clicks a link, Meta adds ?fbclid=IwAR... to the landing page URL. The Meta pixel stores the value in the first-party cookie _fbc, with a prefix and the time of the click: fb.1.1731753600000.IwAR.... It also sets _fbp, an identifier for the browser. With the Conversions API, both are sent as fbc and fbp.

Why it matters

Meta matches server events to its users through identifiers like these and through hashed contact data. Sending fbc improves the match and with it the event match quality. One catch: Facebook also adds the fbclid to links in ordinary posts. An fbclid on its own doesn't prove an ad click. That's why TSO treats it as an organic visit unless something else points to an ad, and builds fbc from the click even when no Meta pixel runs on the page.

Example

Someone clicks a Meta ad on Monday, looks around and leaves. On Thursday they come back directly and send an inquiry. The _fbc from Monday is still there, the Conversions API sends the lead with that value, and Meta credits the ad. If an ad blocker had stopped the pixel on Monday, the cookie would be missing. Then it only works if the fbclid was captured some other way on the first visit, for example by your own tracking.

Common mistakes

  • Counting every fbclid as an ad: organic posts get the same identifier. To assign the channel, you also need UTM parameters.
  • Changing the value: Meta treats it as case-sensitive. A shortened or lowercased fbc no longer matches the click.
  • Preferring an old _fbc: the cookie can come from an earlier click. If the visitor arrives with a new fbclid, the new click counts.

How TSO handles it

Articles on this topic

Related terms

From the term to clean measurement.

TSO connects ads with leads, deals and revenue and reports them back to the ad platforms.