Fix Double Counting Conversions in Google Ads (Shopify)

Before you start ripping out tags, confirm that double counting is actually happening. A few extra conversions here and there might be normal platform behavior — but if Google Ads consistently shows 1.5x to 2x your actual Shopify orders, you have a duplication problem.

The clearest signal is comparing your Shopify order count to Google Ads conversions over a 7-day period. If Google Ads shows 200 purchase conversions but Shopify only processed 110 orders, something is firing twice. A small discrepancy (5-15%) is normal due to attribution differences, but anything above 30% almost always points to duplicate tags.

This is the single most common cause of double counting on Shopify stores. It happens when you have Google Ads conversion tracking set up through Google Tag Manager (GTM) and also have the gtag.js snippet installed directly in your theme or through another app. Both fire on the same purchase event, and Google records two conversions for every single order.

How does this happen? Usually, someone set up GTM-based tracking initially. Later, a different team member (or an agency) added gtag.js directly to the theme.liquid file, not realizing GTM was already handling it. Or an app like Google Analytics or another tracking tool injected the Google tag independently. Either way, you end up with two paths sending the same conversion data to Google.

The tricky part is that each tag might use a slightly different configuration — different conversion labels, different value parameters — which makes it harder to spot in reports. Google doesn't automatically deduplicate hits from different tag implementations unless they pass the same transaction_id.

How to Diagnose:

• Open Google Tag Assistant and place a test order
• On the order confirmation page, look for multiple Google Ads conversion tags (AW-XXXXXXXXX) firing
• Check your page source (View Source or F12 → Elements) for gtag.js snippets — search for 'gtag' or 'AW-'
• In GTM, check if you have a Google Ads Conversion Tracking tag configured for the purchase event
• If you find both a hardcoded gtag.js snippet AND a GTM conversion tag, you've found the duplicate

How to Fix:

• Choose one implementation and remove the other. GTM is generally recommended because it's easier to manage and update without touching theme code.
• If keeping GTM: Remove any gtag.js conversion snippets from your theme.liquid, checkout scripts, and any app settings that inject Google tags. Keep only the GTM container snippet.
• If keeping gtag.js: Remove the Google Ads Conversion Tracking tag from your GTM container. Keep gtag.js as your sole conversion tracking method.
• After removing the duplicate, clear your GTM workspace and publish a new version. Then place a test order and verify only one conversion tag fires using Tag Assistant.

Shopify's built-in Google & YouTube sales channel automatically sets up Google Ads conversion tracking when you connect your Google account. What many merchants don't realize is that this channel installs its own conversion tracking via Shopify's Web Pixel API — and it works in the background without any visible code in your theme.

The problem starts when you (or your agency or a developer) also set up manual conversion tracking through GTM or gtag.js, not knowing the Shopify channel is already handling it. Now every purchase fires two conversion events: one from the Shopify Google channel and one from your manual implementation.

This is especially common after store migrations or agency handoffs. The new team sets up their preferred tracking method without auditing what's already in place. Or a merchant installs the Google & YouTube channel for Google Shopping feeds and doesn't realize it also enables conversion tracking.

How to Diagnose:

• In your Shopify admin, go to Settings → Apps and sales channels and check if 'Google & YouTube' is installed and connected to your Google Ads account
• If it is, check whether it has conversion tracking enabled (it usually is by default when your Google Ads account is linked)
• Then check if you also have manual conversion tracking via GTM or gtag.js
• If both are active, you're double counting

How to Fix:

• Option A (Recommended for most stores): Keep the Shopify Google & YouTube channel for conversion tracking and remove all manual Google Ads conversion tags from GTM and your theme. The Shopify channel uses the Web Pixel API, which is more reliable on modern Shopify checkouts.
• Option B (For advanced setups): Disconnect conversion tracking in the Google & YouTube channel settings (you can keep it for Shopping feeds only) and maintain your custom GTM or gtag.js implementation. This gives you more control but requires ongoing maintenance.
• Never have both active simultaneously. Choose one path and fully disable the other.

Sometimes the tags aren't duplicated — but the conversion actions in Google Ads are. This happens when your account has multiple 'Primary' conversion actions that all track purchases. Each action is counted separately in the Conversions column, so a single order can appear as 2 or 3 conversions.

This typically occurs when someone creates a new conversion action without deactivating or demoting the old one. Maybe you switched from a page-load based conversion to an event-based one, or migrated from an old Google Analytics goal import to a native Google Ads tag. If the old conversion action is still set to 'Primary' and still receiving data (even stale data from cached tags), it inflates your numbers.

Another common scenario: importing conversions from Google Analytics 4 (GA4) while also tracking purchases directly with a Google Ads tag. The GA4-imported conversion and the native Google Ads conversion both count, doubling your numbers.

How to Diagnose:

• In Google Ads, go to Tools → Conversions
• Filter for conversion actions with the category 'Purchase' or 'Sale'
• Check how many are set to 'Primary' — if more than one primary conversion action tracks purchases, that's likely causing inflation
• Also check for GA4-imported purchase conversions that might overlap with native Google Ads conversion tags

How to Fix:

• Keep only one purchase conversion action as 'Primary.' Demote all others to 'Secondary.' Secondary conversions are still tracked and reported separately, but they don't count toward the main Conversions column or influence Smart Bidding.
• If you're importing GA4 purchase conversions AND running a native Google Ads conversion tag, choose one. For most Shopify stores, a native Google Ads tag (or the Shopify Google channel) is preferred because it passes data faster and more reliably.
• Review your conversion actions quarterly. Old, unused actions can accumulate and cause confusion even if they aren't actively double counting.

Even if you only have one tag and one conversion action, you can still see inflated numbers if your implementation doesn't pass a unique transaction_id (also called order_id) with each conversion event. Without this identifier, Google has no reliable way to tell a genuine new purchase apart from a duplicate hit.

Here's a common scenario: a customer completes checkout and lands on the thank-you page. Your conversion tag fires and records the sale. The customer bookmarks the page, or refreshes it, or navigates back and forward. The tag fires again. Without a transaction_id, Google counts both hits as separate conversions. With a transaction_id, Google recognizes the second hit has the same order number and automatically deduplicates it.

This problem is magnified on Shopify because customers often revisit the order confirmation page — they get a confirmation email with a link to check order status, which may route through the same thank-you page URL. Each visit can trigger the conversion tag again.

How to Diagnose:

• In Google Tag Assistant, place a test order and inspect the conversion tag data on the thank-you page
• Look for the 'transaction_id' parameter in the tag payload. If it's missing, empty, or showing a generic value like 'undefined', that's your problem
• In GTM, check your conversion tag configuration — the Transaction ID field should be mapped to a Data Layer variable containing the Shopify order ID
• For gtag.js implementations, verify the transaction_id is being populated in the gtag('event', 'purchase', {...}) call

How to Fix:

• Ensure your conversion tag always passes the Shopify order ID (e.g., order.name or order.id) as the transaction_id parameter. This is the single most important deduplication measure.
• In GTM: Set up a Data Layer variable that captures the order ID from Shopify's checkout data, and map it to the Transaction ID field in your Google Ads Conversion Tracking tag.
• In gtag.js: Include transaction_id in your purchase event: gtag('event', 'conversion', { send_to: 'AW-XXXXX/XXXXX', transaction_id: '{{order_id}}', value: {{order_value}}, currency: 'USD' });
• If you use Shopify's Web Pixel API or the Google & YouTube channel, transaction_id is passed automatically — this is one of the advantages of using Shopify's built-in integration.

Double counting is a configuration problem, and configuration problems tend to recur. You fix the duplicate tag today, then six months later a new developer adds another tracking snippet, or you install an app that quietly injects its own conversion pixel. The cycle repeats.

The root cause isn't any single tag — it's the complexity of managing multiple tracking implementations across theme code, GTM containers, Shopify apps, and sales channels. Every layer you add increases the chance of overlap. The most reliable approach is to consolidate everything into a single, managed tracking pipeline that handles deduplication automatically.