Meta Conversions API Setup for Shopify Merchants
Browser-based Meta Pixel tracking alone tends to undercount conversions today, thanks to ad blockers, Safari's tracking prevention, and shoppers who simply close the tab before a script fully loads. Meta's Conversions API, or CAPI, fixes part of that by sending the same events directly from a server instead of relying only on the shopper's browser, and Pixel Tracker supports it for Facebook alongside the standard pixel.
Setting it up takes a token from Events Manager and a few minutes in Pixel Tracker's dashboard. This guide covers where to find that token, how event_id deduplication keeps a single sale from being counted twice, and how to check whether it's actually improving your match quality.
Why the browser pixel alone isn't enough anymore
Ad blockers, privacy-focused browsers, and Safari's Intelligent Tracking Prevention all interfere with pixel requests before they ever reach Meta, and none of that is something a Shopify store owner can control from their side. Conversions API sends the same event from your server, which isn't affected by what's installed in a shopper's browser, so it fills in gaps the pixel alone will always have.
Getting a Conversions API access token from Events Manager
In business.facebook.com, open Events Manager, select the pixel connected to your store, and go to Settings. Under the Conversions API section, generate an access token and copy it. Paste that token into Pixel Tracker's dashboard under the same Meta Pixel connection, save it, and server-side delivery starts working alongside your existing browser pixel.
How event_id deduplication prevents double counting
When both the browser pixel and Conversions API send an event like Purchase for the same order, Meta needs a way to know it's one sale, not two. Pixel Tracker assigns a matching event_id to both the browser and server versions of the same event, and Meta uses that shared ID, along with the event name and a short time window, to deduplicate them automatically. Without matching event_ids, the same purchase can show up twice in your reporting.
Checking match quality after you turn it on
Events Manager's Diagnostics and Overview tabs show a match quality score for each event, based on how much customer information, like email or phone, was hashed and passed along with it. It's normal for this score to take a few days to stabilize after you add Conversions API, so check back after your store has processed a reasonable number of orders rather than judging it from the first sale.
What server-side tracking doesn't fix
Conversions API improves match rates for events that already have some customer data attached, but it doesn't recover a visitor's activity if they never gave the underlying consent for tracking in the first place, and it isn't a substitute for properly configuring your cookie consent tool. It's also worth knowing that Pixel Tracker's server-side support currently covers Facebook Conversions API and TikTok's Events API, not the other platforms it connects on the browser side.
Step-by-step checklist
- 1
Open Events Manager for your Meta Pixel
Go to business.facebook.com, select the pixel connected to your Shopify store, and open its Settings tab.
- 2
Generate a Conversions API access token
Under the Conversions API section of Settings, generate a new access token and copy it somewhere safe.
- 3
Add the token to Pixel Tracker
Paste the token into Pixel Tracker's dashboard under your Meta Pixel connection and save the change.
- 4
Send a test event and confirm it in Test Events
Trigger a test action on your store and check the Test Events tool in Events Manager for both the browser and server versions of the event.
- 5
Review match quality after a few days
Come back to the Diagnostics or Overview tab in Events Manager once your store has processed several orders to see whether match quality improved.
Frequently asked questions
Where do I get a Conversions API access token for my Meta Pixel?
In business.facebook.com, open Events Manager, select your pixel, go to Settings, and generate the token under the Conversions API section. Paste it into Pixel Tracker's dashboard for that same pixel connection.
Does turning on Conversions API mean I can remove the browser pixel?
No, they're meant to work together. The browser pixel still captures rich on-site behavior, while Conversions API fills in events the browser missed. Removing the browser pixel would actually reduce the data Meta has to work with.
Will I get duplicate Purchase events after adding Conversions API?
Not if event_id deduplication is working correctly. Pixel Tracker sends a matching event_id with both the browser and server copies of the same event, and Meta uses that to treat them as one event rather than two.
Does Pixel Tracker support server-side tracking for platforms other than Meta?
Server-side support currently covers Facebook Conversions API and TikTok's Events API. Google Ads, Snapchat, Pinterest, LinkedIn, and X are tracked through the browser pixel only, not server-side.
How do I know if match quality actually improved after setup?
Check the Diagnostics or Overview tab in Events Manager a few days after enabling Conversions API, once your store has processed a normal run of orders. See the server-side tracking guide for a deeper walkthrough of what the score means.