The Meta pixel alone misses up to 60% of your conversions. Ad blockers block it. Safari's ITP limits it. iOS 14.5+ ATT gates it behind a consent prompt that most users decline.
The fix is the Meta Conversion API (CAPI) — a direct, server-side channel between your website and Meta's servers. LeadSignal wires this up automatically. Here's exactly how to do it.
What Is the Meta Conversion API?
The Conversion API is Meta's server-side event endpoint. Instead of sending conversion data from the user's browser (where it can be blocked), your server sends it directly to Meta over a secure HTTPS connection.
The result: conversion events reach Meta regardless of whether the browser pixel fired or was blocked. Combined with event deduplication, you get complete, accurate signal without double-counting.
LeadSignal runs both channels in parallel — browser pixel for real-time matching, CAPI for resilience — and deduplicates automatically using a shared event_id.
Why the Browser Pixel Alone Is Not Enough
Before the iOS era, a browser pixel was sufficient. A small JavaScript tag fired on your thank-you page, and Meta had the data.
Today that flow breaks in at least three ways:
Ad blockers intercept the pixel request before it leaves the browser. uBlock Origin, Brave's shield, and browser-level blocking combined affect roughly 30-40% of desktop traffic.
Safari ITP limits first-party cookies to 7 days and blocks third-party cookies entirely. If a visitor takes more than a week from first click to conversion, the pixel loses attribution.
iOS ATT means Apple device users see a consent popup before any cross-app tracking is allowed. Opt-out rates are roughly 75-85%, making pixel data on iOS almost useless for retargeting.
Cookie Banner - necessary because of GDPR regulations. But if you visitors decline cookies then there is no change for your Meta Pixel to track any conversion. Around 30% of all website visitors decline cookies by default.
Server-side events bypass all of this.
Prerequisites Before You Begin
You need:
- A LeadSignal account with your website's tracking script installed
- A Meta Business Manager account
- A Meta pixel already created in your Events Manager
- Admin access to the pixel (to generate a CAPI access token)
Your LeadSignal project must already be tracking at least one event (page view, form fill, or custom click event) before you connect CAPI — otherwise there's nothing to forward.
Step 1: Open the Meta Integration in LeadSignal
Log in to your LeadSignal dashboard and navigate to your project. In the left sidebar, select Integrations.
You will see cards for each supported ad platform. Click on Meta Pixel + Conversion API.
Step 2: Enter Your Meta Pixel ID
Your Pixel ID is a 15-16 digit number found in Meta Events Manager:
- Go to Meta Events Manager
- Select your pixel from the left sidebar
- The Pixel ID appears in the top-left corner of the overview
Copy that ID and paste it into the Pixel ID field in LeadSignal.
Step 3: Generate a Conversion API Access Token
Still in Meta Events Manager:
- Click Settings in the left navigation
- Scroll to the Conversion API section
- Under Set up manually, click Generate access token
- Copy the token
Back in LeadSignal, paste the token into the CAPI Access Token field.
This token is a long-lived credential that authorises LeadSignal to send server-side events on behalf of your pixel. Store it securely — it does not expire, but you can revoke and regenerate it at any time from Events Manager.
Step 4: Map Your Conversion Events
LeadSignal needs to know which of your tracked events should be forwarded to Meta, and under which Meta Standard Event name.
In the integration settings, you will see a mapping table. For each event you want to forward:
- Select the LeadSignal event from the dropdown (e.g. "contact_form_submitted")
- Select the corresponding Meta Standard Event (e.g. "Lead")
- Optionally assign a conversion value and currency for purchase-style events
Common mappings:
| LeadSignal event | Meta Standard Event |
|---|---|
| Page view | PageView |
| Form submission | Lead |
| Demo booked | Schedule |
| Purchase | Purchase |
| Add to cart | AddToCart |
You can also map to custom Meta event names if your campaigns use them.
Step 5: Enable the Integration
Toggle the integration Active and click Save.
LeadSignal will immediately begin forwarding server-side events for all new conversions. There is no deploy step, no code change, and no cache to flush.
Step 6: Verify in Meta Events Manager
Give the integration a few minutes, then visit a page on your site and trigger a conversion event (fill out a test form, click a tracked button, etc.).
In Meta Events Manager:
- Click Test Events in the left navigation
- Look for your event in the Server column of the event log
You should see your event appear with a green "Received" indicator. If it shows under both the Browser and Server columns, deduplication is working — Meta will count it once.
Understanding Event Deduplication
When both the browser pixel and CAPI fire for the same user action, Meta would count two conversions unless told otherwise. LeadSignal prevents this by:
- Generating a unique
event_idfor every tracked action - Including that
event_idin both the browser pixel payload and the CAPI server request - Meta's system matches on
event_idand deduplicates automatically
You do not need to configure anything — deduplication is handled automatically.
What to Expect After Setup
Most advertisers see measurable improvement within one or two campaign cycles (typically 7-14 days). The algorithm needs time to re-learn with the improved signal.
Typical outcomes after CAPI setup:
- Reported conversion volume increases — you are now capturing events that were invisible before
- CPA appears to drop — because the algorithm optimises toward audiences that actually convert
- ROAS improves — ad spend shifts toward campaigns with better real-world performance
The pixel-only baseline you were working from was incomplete. CAPI gives the algorithm the full picture.
Next Steps
With Meta CAPI running, consider setting up the same server-side channel for your other platforms. LeadSignal supports Google Enhanced Conversions, LinkedIn CAPI, and TikTok Events API with the same one-dashboard setup. Every platform benefits from the same principle: browser signal for speed, server signal for completeness.