The click identifier was never stored
The visitor arrived from an ad, but the click information vanished before the form or CRM record was created.
Meta CAPI troubleshooting
Fix “No Attribution Data” at the source.
A conversion can reach Meta and still provide weak attribution. Trace what disappeared between the ad click, landing page, form submission, CRM, and server event.
Trace every handoff Keep source context Validate the final payload
Attribution trace6 checkpoints
01Landing URLCaptured
02Click identifierCaptured
03Browser IDsCaptured
04Form payloadCaptured
05CRM recordReview
06Server eventReview
Where tracking breaks
Delivered does not always mean attributable.
A successful API response confirms delivery. It does not prove that Meta received enough context to connect the event to the original ad interaction.
A redirect removed the query parameters
The first landing URL contained attribution data, but a route change failed to preserve it.
Browser identifiers were not passed
The server event was disconnected from useful browser-side context.
The event source was incomplete
The payload did not clearly identify where the conversion happened.
The workflow started too late
The CRM knew a lead converted but had no access to the lead’s original website visit.
The wrong event was inspected
A test event, browser event, and production server event can look similar while carrying different fields.
The controlled path
Move from a loose collection of signals to one traceable event.
Simple CAPI keeps the implementation focused: capture the useful data, connect it to the conversion, send it through a protected endpoint, and validate the result.
Inspect the original landing URL
Confirm the ad click identifier and UTMs are present before any redirect.
Store attribution early
Persist useful browser and campaign values before the visitor submits anything.
Carry the values through the CRM
Map the fields through the form, contact record, webhook, and workflow.
Inspect the final server payload
Verify the exact event sent to Meta, not merely the source form data.
event_name Lead
event_id lead_8e71c4
event_source_url https://example.com/offer
fbclid / fbc present when available
fbp present when available
client_user_agent present
email / phone normalized + hashed
UTM parameters preserved for reportingPractical coverage
Check these values before blaming Meta.
Use accurate values, preserve ownership, and validate the event before relying on campaign reporting.
Original landing URLFBCLID and FBCFBP browser IDUTM parametersEvent source URLClient user agentNormalized identity dataStable event ID
Built for controlled implementation.Keep client credentials out of page code, collect only permitted data, and preserve a clear boundary between client configurations.
Review privacy principles Frequently asked questions
The parts people usually discover after launch.
Resolve the implementation details before the campaign starts spending money.
What does “No Attribution Data” mean?+
It generally means the event lacks enough usable context to connect it confidently to an ad interaction or browser session.
Can an event be received without being attributed?+
Yes. Delivery and attribution are separate. Meta can receive the event while still having limited information for matching or campaign attribution.
Is FBCLID always available?+
No. It may be absent because the visit did not come from a Meta ad, consent or browser conditions limited it, or a redirect removed it.
What is the difference between FBCLID and FBC?+
FBCLID is the click identifier commonly found in the landing URL. FBC is the formatted browser value that can be derived or stored for Meta matching when appropriate.
Can UTMs replace Meta click identifiers?+
No. UTMs are useful for your own reporting, but they do not replace Meta-specific click and browser identifiers.
What results has Simple CAPI produced?+
More than 25 tested client implementations completed with the Simple CAPI method reached at least 9.3 Meta Event Match Quality for their configured Lead and Schedule events.
Simple CAPI workspace
Build the event once. Hand off one controlled installation.
Create a client-specific Lead or Schedule endpoint and validate the exact event Meta receives.
Create your endpoint First eligible script is free after account verification.