Is our tracking setup complete enough (Conversions API, deduplication, match quality)?
Our answer
Run the Conversions API alongside the Meta pixel with a shared event ID. Keep purchase event match quality above 5 (Common Thread Collective aims for 7). At larger scale, add a dedicated server-side tool and a specialist monitor.
- Confidence
- Medium
- Strongest proof
- 8 Meta rules
- 10 practitioners, 6 opinions or claims
- Sources
- 13 sources
- 24 statements
M
DN
New here? Take the 1-minute tour
Why this is the answer
3 reasons and our judgmentMeta's own lift tests set the minimum tracking setup. Its Conversion Lift guide asks for the Conversions API with event match quality above 5.
Missing purchases make existing customers look new. Meta's acquire new customers setting excludes everyone your pixel or Conversions API has seen buy in the chosen window, 730 days by default, according to Meta ads educator Jon Loomer.
Server-side events match far better than pixel tracking, whose match rates have fallen lower than ever, says HexClad. HexClad and Ridge, both consumer brands, run a dedicated server-side tool.
Our judgment
We read Ridge's and HexClad's setups as the pattern for larger brands, which add a dedicated server-side tool and outside monitoring. Ridge also pays an outside firm to monitor pixel signal. We also stretch Common Thread Collective's advice to audit pixel and Conversions API coverage before turning on new-customer targeting for Black Friday to cover any big change.
Our judgment, built from Ridge, HexClad and Common Thread Collective: our reading of these sources, not a finding from any one of them.
What the sources say
24 statements from 13 sourcesMeta's Conversion Lift has no extra cost. As a guide, the account needs a campaign from the past year with $5,000+ spend and 500+ conversions, plus Conversions API with event match quality above 5.
“There’s no additional cost for the test, but ad campaigns or sets you use for conversion lift tests may have certain budget requirements.”
Meta's help page says on-device conversion measurement is on by default, is not active in the EU and UK, works alongside the Pixel and Conversions API, and does not change attribution windows or models.
“Measuring conversions on customer devices affects which conversions can be measured, not how they're credited to your ads.”
WordStream says to run the Meta Pixel and Conversions API together, turn on advanced matching, track fewer meaningful events, and expect some gap between store sales and Meta's numbers.
“combining both Pixel and Conversions API is now considered a best practice for maintaining data accuracy.”
Pilothouse says that before BFCM, deduplicated Meta Purchases should capture at least 90% of eligible Shopify online-store purchases; more points to duplicates, fewer to tracking gaps.
PPC Land says that from November 12, Meta's on-device conversion counting will make campaigns look like they sell a little more, while attribution windows and models stay the same.
“Nothing about the campaigns will have changed. What changes is the counting.”
PPC Land reports that from November 12, 2026 Meta will measure some purchases on shoppers' devices, on by default and switchable per dataset. Whether it feeds bidding or only reporting is unknown.
“I wouldn't opt out by default”
CTC's podcast hosts say brands should share as much customer data as is appropriate, such as hashed email and phone, between Shopify and the Meta pixel.
“We want to share the maximum amount of information between Shopify and the meta pixel.”
Stape, which sells server-side tracking, relays that Meta's on-device conversion matching starts November 12, 2026, on by default outside the EU and UK, and may lift reported conversions without real sales changing.
“advertisers may see an increase in attributed conversions and reported conversion value.”
Shopify's Meta channel turns on direct checkout on Meta surfaces such as Muse by default for eligible stores. Google Analytics and custom pixels do not fire there, and orders are attributed to Meta.
“Google Analytics and custom pixels won't fire in Meta's direct checkout.”
CTC says Meta's AI-generated pages do not load your tag manager or pixel, and most CAPI setups need a browser event, so sales can go unrecorded. It flags gaps over 15% and match scores under 7.0.
“most CAPI implementations rely on a browser event on your domain to trigger the server-side send”
Meta says advertisers need take no steps for web events to go through Aggregated Event Measurement. The 8-event prioritization and value sets are no longer required, and the Events Manager tab has been removed.
“there are no steps you need to take for your events to be processed through Aggregated Event Measurement.”
Meta says Ads Manager results are usually lower than Events Manager counts because Events Manager shows most events received, while Ads Manager shows only attributed events.
“Events Manager shows most events that have been received, while Ads Manager and Ads Reporting show attributed events”
Jon Loomer says Meta's "Acquire new customers" setting now automatically excludes purchasers in your conversion data from the last 730 days, and this can't be turned off. Offline buyers still need a custom audience.
“Customers from your conversion data (730 days)”
CTC says for Black Friday 2026 to turn on new customers only in every prospecting ad set, after checking pixel and Conversions API coverage and uploading about two years of buyers, with a separate retention campaign.
“Without lifecycle controls, Meta's optimization engine defaults to finding the easiest conversions.”
CTC says Meta's Customer Lifecycle Strategy, open to all advertisers from Oct 7, 2026, lets manual Sales ad sets target only new customers, defined at launch as no purchase in the last 180 days.
Jetfuel, an agency, says to run the Meta Pixel and Conversions API together with a shared event ID and name, check deduplication in Test Events, and pass hashed customer details to raise match quality.
“Run the Pixel and CAPI together, never as substitutes”
A podcast guest says you typically want a Conversions API signal score of at least 8 or 9 out of 10.
“You typically want to see like an eight or nine score, at least out of 10”
Jon Loomer says badly configured deduplication of events sent from more than one source inflates Meta's conversion reporting.
“This is one of the most common causes for Meta reporting results that didn't happen.”
HexClad runs Elevar for server-side tracking because pixel match rates have fallen, and server-side events match far more shoppers and send more signal to ad accounts. It gives no match figures.
“The enhanced match rates send more signals to your ad accounts for stronger machine learning and, thus, targeting.”
Jon Loomer says the Meta Pixel alone is not enough and advertisers should also send first-party events through the Conversions API.
“But the Pixel alone isn't enough these days. So make sure you pass first party events from the conversions API.”
A Marketing Operators host says event matching tools such as Elevar or Blotout, which raise match rates, are worth having for most brands, perhaps even those not yet at scale.
“I do think event matching tools are properly rated”
Tony Chopp states agency practice with no account data: keep Event Match Quality at 7 out of 10 or higher, and audit purchase signal integrity at least monthly.
“If Meta is only receiving 80% of your actual purchase events, it is optimizing on incomplete data”
Ridge runs Elevar for tags and pixels and pays an outside firm, Interface Division, to monitor and fix pixel signal problems.
“Helps monitor and fix any pixel issues, and is a resource for the team whenever we have weird new signal engineering ideas.”
Wicked Reports, an attribution vendor, says Conversions API purchases should match Shopify orders within a few percentage points, with matching event IDs, and to decide on your own revenue data.
“within a few percentage points”
In the full answer
For readers who sign in- What to do this week3 steps
- The numbers behind it3 figures from cited sources
- How sure we areWhat its confidence rests on