Meta Conversions API for Landing Pages: Server-Side Tracking Setup Guide
Set up Meta Conversions API on a landing page: server-side tracking, Facebook CAPI setup, deduplication and Event Match Quality.
Written by
Share this
Unlock exclusive Atomicat content
Beyond the blog (/blog), browse our free marketing resources and free tools for calculators and templates (/templates). If you came here searching for landing page tips or landing page best practices specifically, start with the pillars above before browsing further. Browse /resources and /tools.
If your Meta Ads reports show fewer purchases than your checkout does, you are not imagining it. Browser privacy features, ad blockers and consent rules stop the Meta Pixel from seeing a share of your conversions. Meta then optimises on incomplete data, and your cost per result goes up. The fix is the Meta Conversions API (CAPI), which sends events from your server instead of relying only on the visitor's browser. This guide walks through a Meta Conversions API landing page setup step by step: how server side tracking works, the four ways to do a Facebook CAPI setup, deduplication, Event Match Quality and how to keep UTMs intact so you can trust your attribution again.
To put this into practice, explore conversion tracking with AtomicPixel in Atomicat.
Why the Meta Pixel alone is no longer enough
The Meta Pixel is a piece of JavaScript that runs in the visitor's browser. When it works, it sends page views, leads and purchases to Meta. But several things now stop it from working:
- Ad blockers and privacy browsers block requests to known tracking domains.
- Browser tracking prevention limits cookies and shortens their lifespan.
- Consent rules mean some visitors decline tracking, and the pixel must respect that.
- Network and page issues: if the visitor closes the thank-you page before it loads, the purchase event never fires.
The result is conversion tracking that ad blockers and browsers quietly erode. Meta optimises toward the conversions it receives, so missing events do not just make reports wrong. They make delivery worse. After the Meta Andromeda update, where the system leans heavily on conversion signals to judge creatives, that gap matters even more.
How a server side tracking landing page setup works
Server side tracking means your server (or a server you control) records the event and sends it directly to Meta through the Conversions API. A typical flow on a landing page funnel:
- A visitor submits a lead form or completes a purchase.
- Your server, checkout or form tool records the event with its details.
- The server sends the event to Meta's Conversions API, including hashed customer information and browser identifiers.
- The browser pixel sends the same event as usual, when it can.
- Meta matches the two copies by event ID and keeps one.
This is why Meta recommends a redundant setup: pixel and Conversions API together, not one or the other. The pixel captures rich browser context; the server catches what the browser misses.
Before you start: what you need
- Access to Meta Events Manager with admin rights to the dataset (pixel).
- A verified domain in Meta Business Manager.
- A list of the events you want to send (for most landing page funnels: PageView, ViewContent, Lead, InitiateCheckout, Purchase).
- Access to your landing page, form tool or checkout settings, or a developer for a direct integration.
- A consent approach that matches your markets (for example, GDPR in Europe).
4 ways to do a Facebook CAPI setup
1. Partner integration
Many platforms (checkouts, e-commerce platforms, page builders, form tools) offer a built-in Conversions API connection. You paste a dataset ID and an access token, choose events and switch it on. This is the fastest Facebook CAPI setup and the best place to start if your tools support it.
2. Conversions API Gateway
Meta's Conversions API Gateway runs on a cloud account you control and mirrors your pixel events to the server automatically. It needs little code but has a hosting cost and some setup in your cloud provider.
3. Server-side Google Tag Manager
If you already use Google Tag Manager, a server container can receive events from the browser and forward them to Meta's Conversions API. It is flexible and works for many platforms at once, but you need to host the server container and maintain the tags.
4. Direct API integration
A developer sends events from your back end straight to the Conversions API. It gives full control and the best data quality, especially for purchases confirmed by your payment system, but it takes the most work.
Method
Effort
Cost
Control
Best for
Partner integration
Low
Usually included
Medium
Most landing page and checkout funnels
CAPI Gateway
Lowβmedium
Cloud hosting
Medium
Pixel-heavy sites without dev resources
Server-side GTM
Mediumβhigh
Server hosting
High
Teams already on GTM with several ad platforms
Direct API
High
Developer time
Highest
Custom back ends and high-volume advertisers
Step-by-step Meta Conversions API landing page setup
These steps apply whichever method you choose.
Step 1: Choose your events and parameters
For each event, Meta's best practices ask you to send:
- event_name (for example Lead or Purchase), identical to the pixel's event name;
- event_time, sent as close to real time as possible;
- action_source (website, for landing page events);
- event_source_url and client_user_agent for website events;
- event_id, to deduplicate with the pixel;
- customer information such as email and phone, hashed before sending, plus IP address, and the fbp and fbc browser identifiers when available;
- for purchases, value and currency.
Step 2: Generate an access token and connect
In Events Manager, open your dataset, go to settings and generate a Conversions API access token, or connect through your partner integration. Store the token securely; it gives write access to your dataset.
Step 3: Set up deduplication
This is where most setups go wrong. If the pixel and the server both send a Purchase without matching IDs, Meta counts two purchases. To deduplicate:
- send the same event_name from both pixel and server;
- generate one event_id per event (for example the order ID or a random unique string) and pass it to both the pixel call and the server call.
Meta also accepts a combination of external_id and fbp for deduplication, but event_id is the most reliable approach.
Step 4: Capture and pass fbp, fbc and UTMs
The fbp cookie identifies the browser and fbc stores the click ID from the ad (the fbclid parameter). Capture them on the landing page and pass them through your form or checkout so the server event includes them. Meta notes that these values can change, so refresh them rather than storing them forever.
At the same time, preserve UTM parameters from the first landing page through every step of the funnel to the purchase. Many funnels lose UTMs at the jump from landing page to checkout, which breaks attribution in every tool, not just Meta. In Brazil, many advertisers also use UTM-based sales tracking tools such as UTMify to reconcile sales with campaigns, which only works if UTMs reach the checkout intact.
Step 5: Test events
Use the Test Events tool in Events Manager. Submit a real test lead or purchase with your own details, then confirm that:
- the event arrives from both browser and server;
- it shows as deduplicated;
- parameters (value, currency, hashed email) are present.
Step 6: Check Event Match Quality
Event Match Quality (EMQ) is a score out of 10 that Meta shows for each web event. It reflects how well your customer information lets Meta match events to people. To raise it, send more high-quality identifiers (email, phone, name, IP address, fbp, fbc), all correctly hashed where required. Events with only broad information such as location and user agent may be rejected.
Step 7: Monitor weekly
Compare Meta's reported conversions with your back-end orders or leads each week. A small gap is normal. A sudden widening gap usually means a broken event, an expired token or lost parameters after a page change.
Conversion tracking, ad blockers and consent
Server side tracking makes conversion tracking far more resilient to ad blockers and browser limits, because the server copy of each event never depends on the visitor's browser. But it does not override consent. If a visitor declines tracking where consent is required, you must respect that on the server too. Build your consent banner into the landing page, pass the consent state to your server events, and send only what the visitor allowed. Our guide to GDPR-compliant lead capture pages covers the consent side in more detail.
For practical guidance, see our guide to what counts as a landing page conversion.
Server side tracking landing page checklist
Use this checklist after every page launch or funnel change. A server side tracking landing page setup can break silently when someone edits a form, swaps a checkout or changes a domain.
- β The pixel and the Conversions API both fire on every key event (Lead, InitiateCheckout, Purchase).
- β Event names match exactly between browser and server.
- β Every event carries a unique event_id shared by both copies.
- β Email and phone are hashed before they are sent.
- β fbp and fbc are captured on the landing page and reach the server event.
- β UTM parameters survive from the first page to the purchase.
- β Purchase events include value and currency.
- β Test Events shows the event as received from both sources and deduplicated.
- β Event Match Quality has not dropped since the last check.
- β Consent choices are respected on both the browser and the server side.
Meta Conversions API landing page setup for different funnel types
The right Meta Conversions API landing page configuration depends on what the page does:
- Lead generation pages: the key server event is Lead, sent when the form is submitted and stored. Include hashed email and phone, because lead pages usually collect both, which helps Event Match Quality.
- Quiz funnels: send a Lead event when the visitor submits their email, and consider custom events for quiz completion or result type. These help you see which results lead to sales.
- VSL and sales pages: send ViewContent when the page loads and InitiateCheckout when the visitor clicks to the checkout. Purchase should come from the checkout or payment system, the most reliable source.
- E-commerce product pages: send ViewContent and AddToCart with product IDs, and Purchase from the order system with value and currency.
In every case, the most trustworthy Purchase event is the one your payment system confirms, not the one a thank-you page fires.
Common Conversions API mistakes
- No deduplication, so purchases are counted twice and ROAS looks better than it is.
- Different event names between pixel and server (for example "Purchase" versus "purchase_complete").
- Unhashed personal data, which breaks Meta's requirements.
- Lost UTMs and fbclid between landing page and checkout.
- Sending events hours late in daily batches instead of near real time.
- Never checking EMQ after the first setup.
Where Atomicat fits
When your landing page, checkout and tracking live in different tools, every hand-off is a place where UTMs, click IDs and events can be lost. Atomicat keeps them in one funnel. AtomicPixel tracks scrolls, clicks, CTA interactions and conversions in real time, maps multi-touch conversion paths, integrates with the Facebook Pixel, Google Analytics and Google Ads, and is designed to track without third-party cookies, with built-in consent management. Browser and server-side events are both supported, so conversions can still register when browser-side tracking is blocked. Checkout events from AtomicPay connect to AtomicPixel, so revenue can be traced back to a campaign, segment or quiz result without stitching tools together. After Andromeda, those cleaner signals matter more; pair this setup with a Meta Andromeda landing page system so the events you recover still match the creative that earned the click.
Conclusion
A Meta Conversions API landing page setup is no longer optional for serious advertisers. Run the pixel and the Conversions API together, deduplicate with event IDs, pass hashed customer information and browser identifiers, keep UTMs intact to the checkout and watch Event Match Quality. Do that, and Meta optimises on data much closer to reality, which shows up in lower costs and more reliable reports.
Frequently asked questions
How long does a Facebook CAPI setup take?
With a partner integration, often under an hour, including testing. A Conversions API Gateway or server-side Google Tag Manager setup usually takes a day or two. A direct developer integration can take a week or more, depending on your back end.
Can I send offline or phone sales to Meta through the Conversions API?
Yes. The Conversions API accepts events that happen outside the website, such as phone orders or in-store sales, as long as you send the correct action_source and customer information so Meta can match them to ad exposure.
What is a good Event Match Quality score?
Higher is better, and scores of around 6 or above out of 10 are generally considered solid for purchase events. Focus on improving the inputs (email, phone, IP, fbp and fbc) rather than chasing a specific number.
How does the Conversions API handle visitors who reject cookies?
It sends only what you tell it to send. If a visitor declines tracking where consent is required, your server should not send their events to Meta, or should send only what your legal basis allows. Pass the consent state from your banner to the server so both pixel and server follow the same choice.
Will the Conversions API fix attribution in Google Analytics too?
No. The Conversions API only sends data to Meta. Google Analytics and Google Ads have their own server-side options. Keeping UTMs intact through your funnel helps every tool, so treat UTM preservation as a separate, shared fix.
Published
August 17, 2026
Categories
Related Articles
Discover more insights and strategies to grow your business.
