An e-commerce team came to us last April spending $48,000 a month on Google Ads with a reported ROAS of 1.8x. After we dug into their tag setup, we found the real ROAS was closer to 3.2x. The difference? Tag sequencing errors were double-counting conversions on some transactions and missing others entirely.
What Are Tag Sequencing Errors, Really?
Picture this. Your checkout page fires a Google Ads conversion tag, a Meta pixel event, and a GA4 purchase event. They're all supposed to fire after the payment processes. But what if the Meta pixel fires before the payment confirmation returns? Or what if GA4 fires twice because a redirect reloads the confirmation page?
That's tag sequencing in a nutshell. It's about the order your tracking scripts execute, and when they go wrong, your data gets messy fast.
I've personally audited over 200 tag setups in the last two years. Roughly 60% had at least one sequencing issue. Most teams had no idea.
The $10K Discovery
Back to that e-commerce team. They used Google Tag Manager with a standard setup. Their conversion tag was set to fire on the "thank you" page URL. Simple enough. But their payment processor sometimes redirected through an intermediate confirmation step before landing on the thank-you page, which meant the tag occasionally fired on the redirect and then again on the final page.
The result was inflated conversion numbers in Google Ads, which meant their automated bidding was making decisions based on bad data. They were overbidding on keywords that weren't actually performing well, and underbidding on ones that were.
Once we fixed the sequencing (firing the tag only after a dataLayer push confirming the actual transaction), their bidding algorithm recalibrated over about two weeks. Monthly spend dropped by $10,000 while revenue stayed flat. Same sales, less waste.
How to Find Tag Sequencing Errors in Your Setup
You don't need to be a developer. Start here:
- Open GTM's preview mode and walk through your checkout flow
- Watch the order tags fire in the tag assistant panel
- Check if any tags fire more than once on the same page load
- Compare conversion counts in your ad platforms against your actual order numbers for the same period (even a week will reveal gaps)
- Look for tags that fire before their trigger condition is truly met
If your Google Ads reports 150 conversions but Shopify (or whatever your source of truth is) shows 130 orders, you've got a problem. That 15% gap is real money.
Preventing Tag Sequencing Errors Going Forward
We always tell clients the same thing: don't fire conversion tags on page loads. Fire them on confirmed events pushed to the dataLayer. A page can reload, redirect, or cache. An event push happens once, at the right moment.
Set up monitoring that checks whether your conversion counts across platforms stay within a reasonable range of each other. FunnelLeaks can alert you when discrepancies appear between your ad platform data and your actual sales data, so you catch tag sequencing errors before they corrupt weeks of bidding decisions.
If you're spending more than $5,000 a month on paid traffic, audit your tags this week. The numbers might surprise you. Get started with FunnelLeaks and stop flying blind on attribution.
