Check the conversion signals sent to Google Ads and Meta.
Your ad platforms optimise on the conversions they receive. We check what your store actually sends to Google Ads and Meta, whether each purchase is counted once, and why platform numbers differ from your orders.
Why the platforms differ from your store
Your store counts orders. Google Ads and Meta count attributed conversions: purchases they can connect to an ad interaction, under their own rules. Even with perfect tracking the numbers differ, because:
- each platform uses its own attribution model and conversion window, and both can claim the same order;
- Google Ads reports conversions against the date of the ad click, not the date of the purchase, so recent days fill in over time;
- visitors who decline consent, or whose browsers block tracking, send fewer or less complete signals;
- refunds and cancellations reduce your store's figures but not, by default, the platforms' counts.
So "Meta reports more purchases than Shopify" is not, on its own, proof of a fault. A repeated transaction_id, a purchase that fires twice in the browser, or a server event that never matches its browser event is. The work is telling those apart.
Common errors
- Two Google Ads conversion actions both counting purchases, both set as primary, so each order counts twice in bidding.
- A purchase conversion with no transaction ID, so Google Ads can't remove duplicates.
- A conversion tag firing on every visit to the order confirmation page, including reloads.
- Meta Pixel and Conversions API both sending
Purchasewith no shared event ID, so Meta can't de-duplicate them. - Two Meta pixels on the same store, one from an old app or agency.
- Purchase value sent without currency, or with a value that doesn't match the order.
- Tags that never fire for visitors who accept consent late, because the consent update arrives after the tag has given up.
Google Ads checks
| Check | Why it matters |
|---|---|
| Conversion actions list | Which actions exist, which are primary (used for bidding) and which secondary, and whether two count the same purchase |
| Count setting | Purchases are normally counted as "every" conversion; leads as "one". A wrong setting changes totals |
| Conversion ID and label | The tag must use the ID and label of the intended action; a stale label sends conversions nowhere useful |
| Transaction ID | Google Ads uses the transaction ID to avoid counting the same order twice, according to Google Ads help |
| Value and currency | The value sent per conversion, and whether it is the order value you intend to optimise on |
| Source of the conversion | Google Ads tag, a GA4 import, or a platform app: one source per purchase, not several |
| Enhanced conversions | Whether it is set up, sending consented, correctly formatted customer data, and what the diagnostics report. See enhanced conversions not working |
| Conversion diagnostics | The status and any warnings Google Ads shows for each action |
See also Google Ads conversions not recording.
Meta Pixel and Conversions API checks
- Pixel installation. Which pixel IDs load, from where (theme, app, GTM), and whether each standard event (
ViewContent,AddToCart,InitiateCheckout,Purchase) fires once. See Meta Pixel isn't firing. - Conversions API. Whether server events are arriving, with the expected event names, values and customer information parameters, and what Events Manager diagnostics report. See Conversions API not receiving events.
- Deduplication. Meta's documentation explains that browser and server events are de-duplicated when they share the same event name and event ID. We check that the browser
eventIDand the serverevent_idreally match for the same purchase. See Meta duplicate purchases. - Test events. Using Events Manager's Test Events tool and the Meta Pixel Helper browser extension to confirm what each source sends.
An illustrative example of a matching browser and server pair:
Browser: fbq('track', 'Purchase', {value: 54.00, currency: 'GBP'}, {eventID: 'order_1043'})
Server: event_name "Purchase" event_id "order_1043" value 54.00 currency "GBP"
Result: same name and ID, so Meta can keep one and drop the other
Consent and deduplication
Consent decides which signals are allowed to leave the browser. We check:
- the Google Consent Mode states (
ad_storage,ad_user_data,ad_personalization,analytics_storage) by default and after a choice; - whether Meta tags respect the same banner choice, since Consent Mode is a Google mechanism and doesn't control Meta by itself;
- whether a server-side setup sends events for visitors who declined, which is a compliance question for your business to decide, not a tracking shortcut.
More detail: Consent Mode v2 checks.
Validation
- Record the current setup and conversion counts for a baseline period.
- Inspect each tag in GTM Preview, Tag Assistant, Meta Pixel Helper and browser network requests.
- Place an approved test order and follow it into Google Ads conversion diagnostics and Meta Events Manager.
- Confirm one conversion per order per platform, with matching transaction or event IDs and values.
- Write up what was confirmed, what was only observed, and what needs time to show in platform reports.
Pricing
Ad conversion check
From £399
One store, one selected measurement problem or coherent group of symptoms across Google Ads and Meta. Written findings and recommended actions.
Check my ad conversionsDefined fix
From £495
An agreed, contained correction, for example removing a duplicate purchase source or adding a shared event ID, with testing evidence.
Request a fixFull Google Ads or Meta rebuilds and custom server-side infrastructure are outside these starting scopes and are quoted separately. We don't promise campaign performance, ROAS or attribution outcomes. See pricing.
Introductory pricing. These are introductory prices for our current service packages. We agree the scope and price with you before work starts. Future prices may change, but an accepted quote won't change without your agreement.
FAQ
Can you make Google Ads, Meta and my store report the same number?
No. They measure different things. We make sure each platform receives one accurate signal per purchase, then explain the differences that remain.
Do you manage ad campaigns?
No. We check and fix the measurement that campaigns rely on. Bidding and creative stay with you or your agency.
Do you need access to my ad accounts?
For a full check, yes: a standard user or read access added from your own Google Ads account and Meta Business settings. We never ask for passwords.
Not sure what's wrong?
Send us your store address. Mikael will look at the public pages and tell you what he can see, and what he can't.