A raw fbclid from a landing-page URL is not automatically the value Meta expects in user_data.fbc. The CAPI field should contain the click-ID cookie value associated with Meta’s _fbc cookie, obtained from that cookie or constructed by an implementation that uses the incoming request context. A CAPI POST can still return HTTP 200 when the request is accepted at the transport/API level; that response does not establish correct attribution or match quality.
What belongs in user_data.fbc?
fbclid is the click identifier that can arrive as a query parameter on a landing URL. fbc is the value associated with Meta’s _fbc cookie and the value sent in the event’s user_data.fbc field. They are related, but they are not interchangeable strings: do not copy the raw query-string value into fbc and assume it is already the cookie value.
As an Amazon Associate I earn from qualifying purchases.
Meta’s Node.js parameter-builder example processes request context, returns cookie values to save, and places fbc in user_data. Meta’s client-side parameter-builder documentation describes collecting and storing an _fbc cookie value using fbclid as an input.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →How to obtain and send the right value
There are two practical routes: read the first-party _fbc cookie, or use Meta’s parameter-builder to collect or construct the value from browser or request context. The builder route is useful when the landing request supplies context that is not available on later page views; Meta’s examples also recommend saving returned cookie values as first-party cookies so they remain consistent across events.
#1 Best Overall
- Capture the landing context. Process the incoming request before redirects or later page views can obscure useful query and cookie data. Meta’s Node.js example handles
fbc,fbp, client IP address, event source URL, and referrer URL from request context. - Obtain the cookie-associated value. Read the existing
_fbccookie or use a builder that derives the value from the incoming context. Do not treat the rawfbclidstring as the finished cookie value. - Persist and reuse consistently. Where your implementation uses the builder, save its returned cookie values as first-party cookies, as Meta recommends, and use consistent values across relevant events.
- Place it in the event payload. Include the value in the event’s
user_data.fbcfield. Meta’s playbook listsfbcas an additional matching parameter and says it is sent un-hashed. - Wait for asynchronous collection when applicable. If using Meta’s client-side builder, await its collection method before reading its values; its documentation warns that a getter can otherwise return an empty or stale cookie while collection is still running.
Why a CAPI POST can return 200 anyway
Meta’s Conversions API: Direct Integration Playbook says: “The Conversions API returns minimal data to conserve network bandwidth. If the event payload is valid, a 2xx HTTP response code is returned.” That response indicates an API-level outcome for the payload; it is not proof that fbc was represented correctly, that the event was matched to an ad, or that the conversion was counted or deduplicated as intended.
The playbook separately identifies required event parameters and says events missing them “will not be processed.” In the inspected section, it does not classify fbc as a required event parameter. Therefore, do not infer that every malformed or missing fbc must produce a particular HTTP status or rejection. A 2xx response and successful attribution are different checks.
How to verify the implementation
- Inspect the exact outbound JSON and confirm
user_data.fbccontains the value associated with_fbcor the builder-produced value, not simply an assumed raw query parameter. - Use Events Manager’s Test Events view to check whether Meta received and processed the event, including whether processing details indicate it was ignored.
- Review Event Match Quality in Events Manager separately. A successful POST alone does not report match quality.
- When browser and server events are both in use, check that the relevant identifiers and event data are consistent; the playbook treats event processing and match quality as separate verification concerns.
Meta’s sources do not establish a percentage for how much attribution or match quality changes when raw fbclid is sent incorrectly as fbc. The reliable diagnostic is to verify the value and inspect Meta’s event diagnostics, rather than assume a fixed impact from the mismatch.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
