What is an FBCLID?
The fbclid is a parameter Meta appends to any link that leaves Facebook or Instagram, from an ad or an organic post. When the visitor lands, the Meta pixel captures it into a first party cookie called _fbc. That cookie, sent along with pixel and Conversions API events, tells Meta which click a later action belongs to.
Why it matters
As third party cookies fade, the click ID is one of the few signals that comes straight from the click itself. Meta ranks _fbc among the strongest parameters for Event Match Quality, which means it directly affects how many conversions are attributed and how well the algorithm learns. Lose it, and a real purchase becomes an anonymous one.
What to check
- The pixel loads on the landing page: before any redirect, so the parameter is captured and not lost.
- _fbc and _fbp travel with CAPI events: the server sends what the browser captured, deduplicated.
- Redirects and consent tools preserve the query string: the same silent failure as with the GCLID.
- GA4 is kept clean: exclude fbclid from URL reporting so page paths do not fragment into hundreds of variants.
The honest view
The fbclid is often treated as URL clutter to be stripped. Strip it, and you throw away match quality you paid for with every click. Keep it, pass it to the Conversions API, and check the Event Match Quality score moved. It is a five minute fix that most accounts never make.