Shopify Ads Tracking Audit: Meta Pixel, CAPI, GA4 and Google Ads

Paid advertising systems make decisions from the conversion data they receive. When Shopify purchase tracking is duplicated, delayed or incomplete, Meta and Google can optimize toward the wrong customers and the wrong orders.

A good tracking audit does not try to force every platform to report the same number. It confirms that each system receives accurate events, values and identifiers, then explains the remaining attribution differences.

The four systems you need to reconcile

Most Shopify stores use at least four reporting systems:

1. Shopify for actual orders, revenue, refunds and customer records
2. Meta Ads for Facebook and Instagram delivery and attribution
3. Google Ads for Search, Shopping, YouTube and Performance Max
4. Google Analytics 4 for website sessions and cross channel analysis

Shopify should be the source of truth for completed orders and collected revenue. Advertising platforms should be used for campaign optimization and attributed performance. GA4 should help explain journeys and channel interaction.

Step 1: Establish a clean Shopify baseline

Choose a recent date range that contains enough orders to investigate. Export or record:

1. Total orders
2. Gross sales
3. Discounts
4. Returns
5. Shipping charged
6. Taxes
7. Net sales
8. New customer orders
9. Returning customer orders
10. Currency

Remove test orders, cancelled orders and transactions that should not train advertising systems.

Do not compare platform revenue with the wrong Shopify metric. Google Ads may receive order value before tax and shipping, while a Shopify dashboard card may show gross sales including different adjustments.

Step 2: Audit the Meta Pixel

Use Meta Events Manager and a real test order to verify the purchase event.

Check that:

1. The Purchase event fires only after a successful order
2. The value matches the completed order
3. The correct currency is sent
4. Product content IDs match the catalogue when dynamic ads are used
5. The event source is the intended pixel
6. No old theme script or duplicate app sends a second purchase
7. Browser diagnostics do not show critical parameter problems

A common Shopify problem is having the Meta sales channel, a third party pixel app and custom theme code active at the same time. All three may send similar events.

Step 3: Audit Conversions API

Conversions API sends marketing events from a server or platform connection. Meta describes it as a more direct connection between business data and its advertising systems.

The browser event and server event should represent the same purchase. They need matching event names and event identifiers so Meta can deduplicate them.

Review:

1. Event match quality
2. Browser and server event coverage
3. Deduplication status
4. Event time accuracy
5. Customer information parameters
6. Test event results
7. Any unsupported or manually altered values

Do not assume that seeing both browser and server events means the setup is correct. Two events without proper deduplication can inflate purchases.

Official reference: Meta Conversions API overview.

Step 4: Audit Google Ads purchase conversions

Open Google Ads conversion goals and identify every purchase action.

For each action, record:

1. Source
2. Status
3. Whether it is primary or secondary
4. Whether it is included in account goals
5. Value setting
6. Count setting
7. Attribution setting
8. Enhanced conversions status

A store may have a native Google and YouTube app purchase, a Google tag purchase and a GA4 imported purchase. If more than one is primary, automated bidding can receive duplicate outcomes.

For ecommerce purchases, the count setting is usually every conversion because each order has value. Confirm the decision matches the business model.

Step 5: Audit enhanced conversions

Enhanced conversions supplement existing conversion tags with hashed first party customer data. Google now supports a unified account level setting that can accept data from website tags and supported data connections.

Check:

1. The feature is enabled for the intended account
2. Customer data terms are accepted
3. Diagnostics show data is being received
4. Email, phone or address data is normalized correctly
5. The implementation does not replace the normal purchase tag
6. Consent requirements are respected

Enhanced conversions improve measurement quality, but they do not fix duplicate conversion actions or incorrect order values.

Official reference: Google Ads enhanced conversions overview.

Step 6: Audit GA4 ecommerce events

GA4 should receive a purchase event with:

1. A unique transaction ID
2. Order value
3. Currency
4. Item IDs
5. Item names
6. Quantities
7. Discounts when applicable
8. Shipping and tax values when intentionally included

The transaction ID is essential. GA4 can use it to reduce duplicate purchase events when the confirmation page is refreshed.

Review DebugView, Realtime and standard ecommerce reports. A Realtime event proves the event arrived, but it does not prove every parameter is correct.

Step 7: Check consent and browser limitations

Consent choices, browser privacy controls, ad blockers and device changes affect observable events. These factors help explain why platform numbers can differ from Shopify even when implementation is sound.

Make sure the store's consent banner and customer privacy settings are connected to the tracking tools used. Do not send restricted data without the required permission.

Step 8: Reconcile the numbers correctly

Build a daily comparison table with:

1. Shopify orders and net sales
2. Meta attributed purchases and value
3. Google Ads conversions and value
4. GA4 purchases and revenue
5. Total ad spend
6. Notes about promotions, outages and tracking changes

Look for patterns, not perfect equality.

When Meta is much higher than Shopify

Possible causes include duplicate Purchase events, broad attribution, test orders, view through credit or server events that are not deduplicated.

When Google Ads is much higher than Shopify

Possible causes include duplicate primary purchase actions, fixed values, GA4 and native tag imports both used for bidding, or transaction values sent more than once.

When GA4 is much lower than Shopify

Possible causes include consent denial, blocked scripts, checkout domain issues, missing transaction IDs or purchase events that fail after payment redirects.

When every ad platform is low

Possible causes include missing tags, consent changes, checkout updates, app removal, theme releases or payment methods that bypass the expected confirmation flow.

Step 9: Validate with real orders

Complete controlled transactions using different devices and payment methods when possible.

For each test, record:

1. Order ID
2. Order value
3. Payment method
4. Device and browser
5. Meta event result
6. Google Ads event result
7. GA4 event result
8. Time until reporting appears

Refund or cancel test orders correctly and exclude them from business reporting.

Step 10: Protect the setup

Create a tracking change log. Record every app installation, theme deployment, consent update, checkout change and conversion action change.

Assign one owner for measurement. Without ownership, multiple agencies and developers may add tags without understanding what already exists.

Final tracking standard

A reliable Shopify setup should produce:

1. One real purchase per completed order
2. Accurate value and currency
3. Stable transaction identifiers
4. Deduplicated Meta browser and server events
5. One intentional Google Ads purchase goal used for bidding
6. Enhanced conversions with healthy diagnostics
7. GA4 ecommerce parameters that support analysis
8. A documented explanation for normal attribution differences

Continue with why Meta Ads, Google Ads, GA4 and Shopify revenue do not match, or use the complete ecommerce paid ads audit checklist.

Book Your Free Profit Audit.