Meta Conversions API (CAPI) for lead forms: send leads without double counting
How to send leads to Meta through both the Pixel and the Conversions API with one shared event ID, get an access token, verify in Test Events, and handle consent for hashed contact data.
Answer: The Meta Conversions API (CAPI) sends events from your server instead of the visitor's browser. Use it together with the Pixel and give both the same event name and the same event ID; Meta then keeps one and discards the duplicate. Leads the Pixel misses (ad blockers, browser tracking limits, closed tabs) are still recorded by the server event.
Why the Pixel alone falls short
The Pixel runs in the visitor's browser. Ad blockers, iOS tracking limits and people closing the tab right after submitting all drop events. Meta then under-reports conversions and optimizes your ads on less data. A server-side copy fills the gap.
What you need
- Pixel (dataset) ID from Meta Events Manager → Data sources.
- Conversions API access token: Events Manager → your dataset → Settings → Conversions API → Generate access token.
- Test event code (optional): shown in the Test events tab, starts with
TEST.
How deduplication works
| Sent from | Event name | Event ID |
|---|---|---|
| Browser Pixel | Lead |
fbq('track', 'Lead', {}, {eventID: 'abc123'}) |
| Server (CAPI) | Lead |
"event_id": "abc123" |
When the same name and ID arrive from both, Meta keeps one. If the IDs differ, or the name differs (for example Lead vs SubmitApplication), the lead is counted twice. Generate one ID in the browser at submit time and pass it to both.
What to put in the server event
event_name(Lead),event_time,event_id,action_source: "website",event_source_urluser_data- sent as is:
client_ip_address,client_user_agent,fbc(click ID cookie),fbp(browser ID cookie) - SHA-256 hashed: phone (
ph, digits with country code, e.g. 821012345678), email (em, lowercased), name
- sent as is:
More identifiers improve Event Match Quality, but settle consent first.
Consent: hashed data is still personal data
Under Korea's Personal Information Protection Act (and most privacy laws), hashing a phone number does not make it anonymous, and Meta is an overseas recipient. A safe setup:
- Add a separate, optional consent for "cross-border transfer for ad measurement": recipient (Meta Platforms), country, items, purpose, retention.
- Include hashed contact details only for people who agreed.
- For everyone else, send the event with IP, user agent and click IDs only.
- Never send health information such as symptoms.
See consent text for lead forms in Korea or generate it with the free consent tool.
Verify
- Add the test event code and submit one test lead.
- In Test events you should see a Browser and a Server event, one marked as deduplicated.
- Remove the test code before going live.
Send outcomes back
When a lead becomes a consultation or a sale, send a custom server event with the same hashed identifiers (or an external ID). Meta can then learn which people go beyond filling the form.
In CutLanding
Paste your Pixel ID and access token in Settings → Connect. After a lead is saved, the Pixel and server events go out with the same ID, hashed contact details are added only for people who gave ad-measurement consent, health data is never sent, and failed deliveries retry for 24 hours.
FAQ
Can I remove the Pixel and use only the Conversions API?
Meta recommends using both with deduplication. Browser data (fbp and fbc cookies) helps matching, and if one side fails the other still records the lead.
My leads are counted twice. Why?
The event names or the event IDs differ between Pixel and server. Use one ID per submission on both sides and the same event name.
What if my access token leaks?
Generate a new token in Events Manager and replace it wherever it is used. Keep the token on the server only, never in page HTML.