Skip to main content
Free checklist

Ecommerce tracking audit checklist

57 checks for verifying your conversion tracking across Meta, Google Ads, Google Analytics 4, TikTok, Microsoft Ads and Taboola, plus server-side delivery, data quality and consent. Each check says how to confirm it in the platform itself. Tick items as you go; your progress stays in this browser.

By Kiril Kostov. Sources checked on .

Which platforms do you advertise on?

Switch off the ones you do not use. The server-side, data quality and consent checks always stay.

0 of 57 checks done
0%

Progress is saved in this browser only. Nothing is sent to SignalBridge.

Meta (Facebook and Instagram)

The Pixel, the Conversions API and the match data that connects the two.

0 of 8

Google Analytics 4

The property, its ecommerce events and the filters that keep it clean.

0 of 7

TikTok

The Pixel, the Events API and the click ID.

0 of 6

Microsoft Ads

The UET tag, conversion goals and the Microsoft click ID.

0 of 5

Taboola

The pixel, the click ID and the event names Realize expects.

0 of 4

Server-side delivery

Checks that apply to any server-side setup.

0 of 6

Data quality and deduplication

Whether the numbers in your platforms agree with your store.

0 of 7

Rather not repeat this by hand?

SignalBridge shows delivery status, failures and Event Match Quality for each destination in one place, so most of the server-side checks are a glance at the dashboard.

Start a 14-day free trial

How to run the audit

The checklist works for any setup, with or without server-side tracking. Run it in this order and it takes less time than going platform by platform with no plan.

  • Switch off the platforms you do not advertise on, so you only see checks that apply.
  • Place a test order and note its order ID, value and time. Most checks use it as evidence.
  • Work through each platform, confirming every item in the platform's own interface.
  • Compare a full week of store orders with the purchases each platform reports for its own campaigns.
  • Fix the failures that cost the most first, then repeat the order comparison.
  • Repeat after any change to the theme, checkout, consent banner or tracking apps.

The failures that cost the most

Not every item carries the same weight. These six distort the numbers you use to spend money, so check them first.

  • Duplicate purchases. Two senders for one order, or a tag plus an import, inflate ROAS and teach the platform to chase the wrong signal.
  • No deduplication between browser and server events. Without a shared event name and event ID, the same sale is reported twice.
  • A missing or wrong value or currency. Platforms optimise on value, and Meta rejects a value without a currency.
  • Click IDs lost between landing and order. The conversion then cannot be matched back to the ad.
  • Expired or revoked access tokens. Server-side events silently stop reaching the platform.
  • Consent not respected on the server. A server-side sender that ignores a visitor's choice is a compliance problem, not just a data problem.

Reading the gap between your store and a platform

A platform will almost never match your store exactly, and that is not automatically a bug. Compare the orders that came from that platform's campaigns, not total orders, and expect some difference from attribution windows, consent choices, blockers, browser restrictions, refunds and time zones.

What matters is the size and the trend. A gap that holds steady for weeks is a property of your traffic. A gap that opens after a theme update, a checkout change or a new consent banner points at something that broke.

How often to repeat it

Run the full list when you set up or change tracking, and a shorter pass monthly: delivery failures, duplicate purchases, expired tokens and the order comparison. Run it before any peak sales period, when a broken setup costs the most.

Questions about this tool

Do I need server-side tracking to use this checklist?

No. Most checks apply to browser-only setups too. The server-side section matters only if you send events from a server, and it is always shown so you can decide whether you need one.

Is my progress saved?

Yes, in your browser's local storage on this device. It is not sent to SignalBridge or anyone else, and clearing site data removes it. If your browser blocks storage, the checklist still works for the current visit.

Where should I start?

Check for duplicate purchases and for a shared event ID between browser and server events. Then confirm value and currency on a test order, and compare a week of store orders with each platform.

Why compare against my store and not against GA4?

Your store is the record of what was sold. GA4 is another tracking system with its own consent and browser gaps, so it cannot settle a disagreement between platforms.

Does the consent section count as legal advice?

No. It lists technical checks. Which regions and categories need consent depends on your business and location, so ask a lawyer.

How long does the audit take?

It depends on how many platforms you run. Walking the checks for one platform with a test order is quick. Comparing a full week of orders with each platform takes longer, and it is where most problems show up.

What if a platform I use is not listed?

The server-side, data quality and consent sections apply to any platform. For the platform-specific part, the same ideas hold: confirm the tag fires, confirm click IDs persist, confirm there is one sender per sale and confirm value and currency.

Sources