How to audit your ad tracking across platforms in one afternoon

Most Shopify merchants audit their ad tracking the same way: open Facebook Events Manager, check that Purchase events are firing, feel reassured, then open Google Ads and repeat the process, then maybe get to TikTok if there's time left. Each check looks fine in isolation. What that approach misses is everything that only shows up when you look at the platforms together: the same Purchase event firing twice through two different apps, a pixel that loads but stopped receiving real conversion data three weeks ago, or a platform you're not even spending on anymore that's still collecting visitor data for no reason. A platform-by-platform audit catches obvious breakage. It doesn't catch overlap, and overlap is where the expensive mistakes live.

The reason this happens is structural, not a matter of carelessness. Each ad platform's help center tells you how to check that platform's pixel, using that platform's tools, inside that platform's dashboard. Nobody's documentation tells you to cross-reference Facebook's reported purchases against TikTok's reported purchases against your actual Shopify order count for the same day. So merchants don't do it, not because it's hard, but because no single source suggests it as a step. The result is a blind spot specific to running multiple platforms at once: each dashboard can report clean data individually while the combined picture is quietly wrong, whether that's double-counted conversions inflating your perceived return on ad spend, or a gap where no platform is reporting a sale that Shopify definitely recorded.

An audit that tries to cover all seven major platforms (Meta, Google Ads, TikTok, Snapchat, Pinterest, X, and LinkedIn) in an afternoon usually means a shallow pass on all of them instead of a real check on the ones that matter. Start with your actual ad spend, not your list of installed pixels. Pull up your ad accounts and see where the last 30 days of budget actually went. Most solo merchants find that two platforms account for nearly all of it, with one or two more pixels installed from a campaign that ended months ago and never got removed. Audit the platforms you're spending on thoroughly. For anything installed but not currently running ads, a five-minute check that the pixel isn't broken is enough, or consider removing it if there's no plan to use it again soon. Depth on two platforms beats a shallow pass on seven.

Once you know which platforms to focus on, the first real check is whether the pixel loads at all. Each major platform has a free browser extension built for exactly this: Meta Pixel Helper for Facebook and Instagram ads, Google's Tag Assistant for the Google Ads conversion tag, and TikTok Pixel Helper for TikTok. Install the one for each platform you're auditing, load your storefront in a normal browser tab (not incognito, since some ad blockers behave differently there), and click through a real session: homepage, a product page, add to cart, and if you're comfortable doing it, checkout. Each extension shows which pixel ID fired and which events it saw. This tells you the pixel is present and technically working. It does not tell you whether the event data it's sending is complete or correct, which is a separate check covered next. A green checkmark in Pixel Helper is a starting point, not a finish line.

The next step moves out of your browser and into each platform's own event manager: Meta's Events Manager, Google Ads' conversion diagnostics, TikTok's Events Manager. This is where a lot of audits stop too early, because PageView is almost always firing (it's the simplest event, and most installs get it right by default), so merchants see PageView data flowing in and assume tracking is healthy. Purchase is the event that actually matters for measuring return on ad spend, and it's also the one most likely to be broken, since it depends on the checkout or thank-you page firing correctly, with the right value and currency attached. In each platform's dashboard, look specifically at Purchase event volume over the last 7 to 14 days and compare it, roughly, against your actual Shopify order count for the same period. If a platform's Purchase count is well below your real order count, something upstream is dropping the event: a checkout page that changed, a consent banner blocking the script before it fires, or an app that stopped working after a theme update. If you'd rather not go dashboard by dashboard, the pixel health check tool runs a storefront scan alongside a short setup checklist and flags a lot of these gaps in a couple of minutes, though it's a starting signal, not a replacement for checking each dashboard directly.

Purchase events being too low is one failure mode. The other, less obvious one is Purchase events firing too many times for the same order, which is common on stores that have accumulated tracking apps over time. It's easy to end up with Shopify's native Facebook & Instagram sales channel sending a Purchase event, a separate pixel app also sending a Purchase event, and a theme customization from two years ago still injecting a third copy, all for the same single order. Each platform then reports that one sale as two or three conversions, which inflates your apparent conversion rate and return on ad spend, and can also throw off that platform's own optimization, since its algorithm is learning from inflated signals. The way to catch this: open your browser's network tab (or use each platform's Pixel Helper, which usually flags duplicate pixel IDs) during a real checkout, and count how many times a Purchase or Complete Payment request fires to the same platform. More than one is a duplicate, and the fix is almost always removing one of the redundant integrations, not adding deduplication logic on top of both. The Meta Pixel troubleshooting guide covers duplicate pixel conflicts specifically if Facebook is one of the platforms showing this. If your store has changed tracking apps more than once, this is the single highest-value thing to check in an afternoon audit, because it directly inflates the numbers you're using to make budget decisions.

The last technical check is whether your tracking still works when the browser pixel doesn't fire at all, which happens more often than most merchants realize. Ad blockers, Safari's Intelligent Tracking Prevention, and a visitor simply declining a consent banner can all stop a client-side pixel before it ever loads. To see this for yourself, install a basic ad blocker extension, turn it on, and repeat the same browsing session from the browser helper step: homepage, product page, add to cart, checkout. Watch whether each platform's Pixel Helper still shows the pixel firing. On most stores it won't, because a standard client-side pixel has no way to route around a blocker sitting in the same browser. This is the actual argument for server-side tracking: instead of relying on a script in the visitor's browser, the conversion event is sent directly from your server to the ad platform, so it isn't affected by what's blocked client-side. Right now, that server-side path is really only mature for two platforms: Facebook's Conversions API and TikTok's Events API. If Meta or TikTok are among the platforms you're spending on, this is worth setting up; for platforms without a comparable server-side option yet, browser-based tracking with the checks above is still the main lever available. Pixel Tracker supports server-side tracking for exactly these two, alongside client-side pixel connections for Meta, Google Ads, TikTok, Snapchat, Pinterest, X, and LinkedIn from one Shopify dashboard, if consolidating that setup is something you're looking to do. It's currently pre-launch, so the waitlist is the way to get access once it opens. For a longer walkthrough of how server-side tracking actually works, the server-side tracking guide covers the mechanics in more detail, and if you want a rough sense of how much browser-only tracking might be costing you before deciding whether it's worth setting up, the tracking cost and coverage calculator estimates a coverage score and a range of likely missed conversions from a few inputs.

An afternoon is enough time to run all of the above on two or three platforms, but not enough time to fix everything you find. If the audit turns up more than one issue, which is common, it helps to prioritize. First, fix duplicate Purchase events, since they're actively distorting the numbers you're using right now to decide where to spend, and the fix is usually just removing a redundant app or theme snippet. Second, fix any platform where Purchase events are firing well below your actual order count, since that's a direct measurement gap on money you're already spending on ads. Third, if Meta or TikTok are among your main platforms and you're not on server-side tracking yet, that's the next highest-leverage fix, since it recovers conversions that ad blockers and browser restrictions are otherwise dropping silently. Everything else, like removing an unused pixel from a platform you no longer advertise on, or double-checking event values match your actual order totals, is worth doing but can wait for a slower week.

None of this requires new tools or a rebuilt tracking stack to get through in one sitting. It requires actually looking at two or three platforms together instead of one at a time, and being honest about what the numbers say when you compare them to your real Shopify orders. Most merchants who run this audit find at least one issue in the first hour. That's usually the point of doing it.