The Pre-BFCM Meta Attribution Audit: 12 Checks to Run Before November 1

Your Meta tracking is ready for Black Friday when three things are true: you know exactly which attribution setting your numbers come from, Meta's purchase count reconciles with your store's orders within a gap you can explain, and you have a baseline locked from before the promo calendar starts. This meta attribution checklist walks through the 12 checks that get you there. It isn't a CAPI setup tutorial. It assumes tracking is installed and asks whether you can trust what it reports.

The stakes are bigger than usual. Adobe projects U.S. shoppers will spend $275.1 billion online between November 1 and December 31, 2026, with social media posting the biggest gain in revenue share. Meta will sit in the middle of many of those journeys, and it will also report how much credit it deserves. Black Friday is November 27, so finishing by November 1 leaves time to fix what you find.

Why does Meta attribution need an audit this year?

Because the definitions changed. In March 2026 Meta narrowed click-through attribution so that, as Social Media Today reported, only website link clicks count as clicks. Shares, saves, and other non-link interactions moved into a renamed bucket called engage-through attribution. Separately, Meta removed the 7-day and 28-day view-through windows from the Ads Insights API and capped how far back some breakdowns go, per PPC Land's coverage of the API changes.

So a BFCM 2025 report and a BFCM 2026 report can both say "7-day click" and still measure different things. (We broke down the details in our post on Meta's 2026 click definition change.)

The 12-point Meta attribution checklist for BFCM 2026

The first six checks confirm the data coming in is clean. The last six make sure you can read it in November.

1. Choose your attribution setting and write it down

What to check: the attribution setting on every active ad set, including the click window, whether engage-through is on, and whether 1-day view is on. Meta's current default is 7-day click, 1-day engage-through, and 1-day view.

Why it matters for BFCM: every ROAS number you report in November inherits this choice. Mixed settings across ad sets make blended results meaningless.

What good looks like: one documented setting per account, shared with everyone who reads the reports.

2. Check Event Match Quality on your Purchase event

What to check: the Event Match Quality score for Purchase in Events Manager, and which customer parameters are actually being sent.

Why it matters: Meta's own guidance says only matched events can be used for attribution and delivery optimization. Low matching means Meta is guessing on a bigger share of your holiday orders.

What good looks like: a stable score over the last few weeks, with email, phone, IP address, and the fbp and fbc browser IDs present on most purchases. A sudden drop after a checkout change is a red flag to chase now.

3. Confirm pixel and server events deduplicate

What to check: whether browser and server Purchase events share the same event name and event ID.

Why it matters: Meta deduplicates on event ID plus event name within a 48-hour window. If those don't match, one order can count twice, and doubled purchases during a sale look exactly like a winning campaign.

What good looks like: Events Manager shows deduplication working on Purchase, and Meta's purchase count never exceeds your actual order count.

4. Audit purchase value math

What to check: what the value parameter on Purchase includes. Pull five recent orders that used a discount code and compare the value Meta received to the order record.

Why it matters: Meta requires a monetary value and a valid currency code on purchases, but it doesn't decide whether that value includes tax, shipping, or the discount. BFCM is discount season. If value is pre-discount gross, Meta ROAS inflates exactly when margins are thinnest.

What good looks like: a written definition (for example, "subtotal after discounts, excluding tax and shipping") that matches what you compare against in your store reports.

5. Lock your UTM and naming conventions

What to check: that every BFCM campaign, ad set, and ad follows one naming pattern and carries consistent UTM parameters.

Why it matters: holiday launches move fast, and duplicated ads with copied UTMs land in "direct" or "unknown" everywhere except Meta.

What good looks like: one agreed template. Our UTM naming convention guide has one to copy.

6. Compare Meta purchases to store orders for the last 30 days

What to check: Meta-reported purchases and revenue against Shopify (or BigCommerce or WooCommerce) orders and revenue for the same 30 days, day by day.

Why it matters: this is the gut check for Meta ads ROAS accuracy. If Meta claims more purchases than your store recorded from all channels on a given day, something is broken.

What good looks like: a gap that is consistent day to day and explainable. A gap that swings wildly is a tracking problem. Our attribution data reconciliation process walks through this step by step.

Find out how far Meta's numbers drift from your real orders before November 1.

See Meta-reported results next to click-only, first-party data on your own account.

Book a demo Start free trial

7. Freeze baseline numbers before promos start

What to check: that you have recorded CPA, ROAS, conversion rate, AOV, and new-customer share for a clean pre-promo window, such as October 1 to 31.

Why it matters: without a baseline, you can't tell whether a campaign worked or the discount did.

What good looks like: a dated snapshot, saved outside Ads Manager, that nobody can quietly overwrite.

8. Review your existing-customer definition

What to check: the audience segments in your ad account's Advertising Settings, specifically which custom audiences and customer lists define "existing customers."

Why it matters: Meta uses these segments for new versus existing customer breakdowns in sales campaigns. A stale customer list makes repeat buyers look like new acquisitions, flattering prospecting results in the season when past customers are most likely to return.

What good looks like: a customer list refreshed in the last few weeks and again before Black Friday.

9. Know your reporting breakdown limits

What to check: which breakdowns and lookbacks your reports depend on. Unique-count fields and hourly breakdowns now max out at 13 months in the API, and frequency breakdowns at six months.

Why it matters: a BFCM 2025 comparison built on live hourly or frequency pulls may already be partly out of reach.

What good looks like: last year's holiday data exported and stored in your own warehouse or spreadsheet, so year-over-year analysis doesn't depend on what Meta still keeps.

10. Separate click, engage-through, and view results

What to check: whether your dashboards can show conversions by attribution type, not just one blended total.

Why it matters: engage-through and 1-day view conversions are the least verifiable. During BFCM, they can swell with purchases that would have happened anyway.

What good looks like: scaling decisions made on click-through results, with engage-through and view reported separately as context.

11. Put independent first-party click tracking in place

What to check: whether you have a measurement source that Meta doesn't control, tracking ad clicks through to actual orders in your store.

Why it matters: every check above still relies on Meta's reporting. Click-only attribution means a conversion gets credited only when a tracked ad click leads to an order, with no view-based credit. It's a second, verifiable read on the same campaigns. On one AdBeacon account, Meta reported a 3.23x ROAS while click-only measurement showed 0.93x.

What good looks like: platform reported ROAS vs actual ROAS shown side by side, live, for every campaign, before November 1.

12. Agree on the decision rules in advance

What to check: that your team and clients agree which number drives budget changes and what triggers a scale or cut.

Why it matters: Black Friday weekend is the worst time to debate which dashboard is right.

What good looks like: one page naming the source of record, thresholds, and who makes the call.

What should you do if the audit turns up problems?

Fix data-in problems first, because dedup errors, wrong purchase values, and low match quality corrupt everything downstream. If checks 1 through 6 pass but Meta's numbers still don't line up with your orders, that is usually not a tracking failure. It's attribution design, and our post on why CAPI is set up but iOS ROAS still looks wrong covers that gap in detail.

You probably won't fix all 12 by November 1. Baselines (check 7), the orders comparison (check 6), and independent tracking (check 11) give the most protection for the least effort.

Get BFCM-ready before the spend arrives

The goal isn't perfect data. It's knowing which numbers you can trust, and by how much, before the biggest spend weeks of the year. Lock your settings, reconcile against real orders, and freeze a baseline while there's still time to act. If you want to see Meta's reported numbers next to click-only, first-party results on your own account before November, book a live AdBeacon demo and we'll walk through it with you.

Frequently Asked Questions

What is a Meta attribution checklist?

A Meta attribution checklist is a structured audit of whether your Meta Ads reporting can be trusted. It covers attribution settings, Event Match Quality, pixel and server deduplication, purchase value accuracy, and how Meta's numbers compare with your actual store orders.

When should I audit Meta tracking before Black Friday?

Aim to finish before November 1. Black Friday 2026 is November 27, and early promotions start well before then, so you need clean baselines and time to fix issues before holiday spend ramps up.

What attribution setting should I use for BFCM?

Pick one setting, document it, and apply it consistently across ad sets. Many ecommerce teams use click-through results for scaling decisions and report engage-through and view-through conversions separately, since those are harder to verify.

Why doesn't Meta's purchase count match my Shopify orders?

Meta credits conversions under its own attribution windows, including engage-through and view-through, and can double count if pixel and server events aren't deduplicated. A consistent, explainable gap is normal; a gap that swings day to day usually points to a tracking problem.

Is this the same as setting up the Conversions API?

No. This audit assumes the pixel and Conversions API are already installed and checks whether the data they send is accurate enough to make budget decisions on during BFCM.