Setting Up Google Ads Conversion Tracking for Your Ecommerce Store

We’ve opened accounts where the campaign looked structured perfectly — good keywords, tight negatives, sensible budget — and it still underperformed, because conversion tracking was never actually verified. Google Ads can’t optimize toward purchases it doesn’t know happened, and no amount of keyword or bidding optimization compensates for the algorithm working blind.

The Two Ways to Track Conversions

• Google Ads tag (gtag.js) — installed directly on your site, fires on specific events like a purchase or a form submission
• Google Analytics 4 linked conversions — set up conversion events in GA4 first, then import them into Google Ads instead of installing a separate tag

For most ecommerce stores, GA4 linked conversions are less error-prone, since you’re managing one tracking setup instead of two tags that can drift out of sync.

Step 1: Install the Base Tag Correctly

Whether you use Google Tag Manager or paste the tag directly, it needs to sit on every page, not just the thank-you page. A tag that only fires on checkout completion can’t build the audience signals Google Ads needs for Smart Bidding — it needs to see the full path, not just the last step.

Step 2: Fire the Purchase Event With Real Values

A conversion event that fires but doesn’t pass the actual order value is close to useless for a store selling different-priced products — Google optimizes toward volume instead of revenue. Pass the transaction value and currency with every Purchase event, the same way we set up Purchase events on the Facebook Pixel for Meta — and the same deduplication logic Conversions API relies on applies here too: one accurate event beats two conflicting ones.

Step 3: Test Before You Trust It

Place a real test order and check:

• Google Tag Assistant (or GA4’s DebugView) shows the Purchase event firing with the correct value
• The conversion shows up in Google Ads within 24 hours under Conversions > Summary
• The order count in the conversion report roughly matches your actual order count for that period — a big mismatch means something’s double-firing or not firing at all

If You Run Both COD and Prepaid

Prepaid orders convert cleanly at checkout. COD orders don’t — the sale isn’t confirmed until the courier actually delivers it, sometimes days later. If you fire the conversion the moment a COD order form is submitted, you’re feeding Google Ads a mix of real sales and orders that will later be returned or refused, which quietly drags down Smart Bidding’s accuracy over time. A more accurate (if more manual) approach is importing confirmed COD deliveries as offline conversions once the return window has mostly closed.

Enhanced Conversions Close a Real Tracking Gap

Beyond the base tag, enabling Enhanced Conversions (which sends hashed, privacy-safe customer data like email or phone number alongside the conversion event) recovers conversions that browser tracking prevention would otherwise silently drop — this has become a meaningfully large gap on its own as browsers restrict third-party tracking further, and turning it on is a one-time setting change rather than an ongoing maintenance task.

View-Through vs. Click-Through Windows

Google Ads counts a conversion within a set window after either a click or, separately, an ad impression the person didn’t click but later converted anyway (a view-through conversion) — the default windows aren’t necessarily right for every business, and a store with a longer typical consideration period benefits from checking these settings rather than assuming the default matches actual buyer behavior. Attributing too much credit to view-through conversions specifically can make display or video campaigns look more effective than they actually are, so this setting is worth understanding, not just leaving on default.

Cross-Device Tracking Has Real Limits

Someone who sees an ad on their phone and completes the purchase later on a laptop is difficult to track as a single journey without the person being signed into a Google account on both devices — Google’s own cross-device reporting fills in some of this gap using signed-in data, but it’s an estimate, not a complete picture. Being aware of this limitation prevents over-trusting a device-level conversion breakdown as if it were fully accurate, when a meaningful share of cross-device journeys simply aren’t captured.

A Common Mistake

Setting up conversion tracking once at launch and never checking it again. A site redesign, a new checkout app, or a Tag Manager change can silently break tracking — recheck it any time conversion numbers look off compared to your own order records.

If it’s impressions dropping rather than conversions specifically, broken tracking isn’t the only possible cause — our Limited Ad Serving policy update covers a separate, quieter reason delivery can shrink even when tracking itself is working fine. Treating conversion tracking as infrastructure that needs periodic verification, not a one-time setup task, is what actually keeps Smart Bidding optimizing against real data month after month. Once tracking is genuinely solid, our Smart Bidding guide covers which automated strategy actually fits — accurate order values specifically are what makes tROAS possible at all, not just tCPA.