How to set up Google Ads conversion tracking on Shopify

Why Track Conversions in Google Ads on Shopify

Running paid ads without conversion data is like driving blindfolded. Google Ads gives you the tools to measure which clicks turn into sales, but the measurements are only useful if they are set up correctly on your Shopify store. Accurate conversion tracking tells you which campaigns, ad groups, and keywords generate revenue, helps you allocate budget efficiently, and improves automated bidding strategies such as Target ROAS. For Shopify merchants who spend on Google Ads, a reliable conversion tag is essential for scaling profitably.

Create a Google Ads Conversion Action

The first step is to define the conversion you want to measure inside Google Ads. Follow these actions to create a purchase conversion:

1. Sign in to your Google Ads account and click the tools icon (🔧) in the upper right corner.
2. Under “Measurement,” select Conversions.
3. Click the plus button (+) and choose Website as the source.
4. Enter a name such as “Shopify Purchase” and select Purchase as the conversion category.
5. Set the value to “Use different values for each conversion” so the actual order total is recorded.
6. Choose a conversion window that matches your sales cycle (30 days is a common default).
7. Leave the attribution model on “Last click” unless you have a specific strategy.
8. Click Create and continue. Google will present two snippets of code: the Global Site Tag (gtag.js) and the Event Snippet for the purchase event.

Copy both snippets. You will paste the Global Site Tag into your Shopify theme and the Event Snippet into the order confirmation page.

Add the Global Site Tag to Your Shopify Store

The Global Site Tag must load on every page of your store so Google can associate clicks with later purchases. Here’s how to add it safely:

• From your Shopify admin, go to Online Store → Themes.
• Find your current theme, click Actions → Edit code.
• Open the layout/theme.liquid file. This file contains the <head> section that loads on every page.
• Just before the closing </head> tag, paste the Global Site Tag you copied from Google Ads.
• Save the file. The tag will now fire on all storefront pages, including product, collection, and blog pages.

If you prefer a plugin‑free approach, you can also use Shopify’s built‑in “Preferences” panel to add the tag under Online Store → Preferences → Google Analytics, but the manual method gives you full control and ensures the tag loads before any other scripts.

Set Up the Event Snippet for Purchase Conversions

The Event Snippet records the actual sale and sends the order value back to Google Ads. Shopify’s order‑status page (the “Thank you” page) is the only place that reliably contains the final transaction amount.

1. From the Shopify admin, navigate to Settings → Checkout.
2. Scroll to the “Order processing” section and locate the field labeled Additional scripts.
3. Paste the Event Snippet you copied earlier into this field. The snippet will look similar to:

   <script>
     gtag('event', 'conversion', {
         'send_to': 'AW-XXXXXXXXX/abcdEFGH1234',
         'value': {{ total_price | money_without_currency }},
         'currency': '{{ shop.currency }}',
         'transaction_id': '{{ order.name }}'
     });
   </script>
   

4. Replace the placeholder variables with Shopify liquid tags as shown above. This ensures the actual order total and ID are passed to Google Ads for each purchase.
5. Click Save. The script will now fire only when a customer reaches the order‑status page, guaranteeing accurate conversion data.

If you use a third‑party app that modifies the checkout flow, verify that the script is still present on the final page. Some apps provide a dedicated “Conversion tracking” field where you can paste the snippet instead of using the default Shopify setting.

Verify Your Conversion Tracking Works

After publishing the tags, you must confirm they are firing correctly. Google offers two free tools for this purpose:

• Google Tag Assistant (Legacy) extension – install the Chrome extension, open your store’s homepage, and check that the Global Site Tag loads without errors.
• Google Ads “Conversions” page – click the “Tag setup” dropdown for the conversion you created and select “Check status.” The tool will show a green checkmark when the tag is detected on the order‑status page.

To perform a real‑world test, place a low‑value order (e.g., $1) using a discount code. After the order completes, return to Google Ads and look for the conversion under “Conversions” > “Recent conversions.” It may take a few hours for the data to appear, but the status indicator should turn green within 24 hours.

For merchants who also run WordPress sites, TraceSignals offers a live pixel tracking solution that works across GA4, Google Ads, and Meta Pixel. Their WordPress plugin automates the same steps described here, saving time and reducing implementation errors.

Tips for Accurate Data and Common Pitfalls

Even after a successful setup, ongoing maintenance is required to keep your data trustworthy. Follow these best practices:

• Avoid duplicate tags. If you previously added a Google Ads tag via an app or theme, remove the old version before installing the new one.
• Use consistent currency settings. Ensure the currency in the Event Snippet matches your Shopify store’s default currency; otherwise Google will record zero‑value conversions.
• Monitor for JavaScript conflicts. Some apps inject scripts that can block the Global Site Tag. Test new app installations on a duplicate theme before publishing.
• Keep your conversion window aligned with your sales cycle. If you offer delayed payment options (e.g., Klarna), extend the conversion window to capture those sales.
• Leverage Google Ads auto‑tagging. Enable auto‑tagging in Google Ads settings so that GCLID parameters are automatically added to your URLs, enabling better attribution.

Finally, schedule a quarterly audit of your conversion data. Compare the total sales reported in Shopify with the conversion totals in Google Ads. Any significant discrepancy usually points to a tag that has stopped firing or a script conflict that needs correction.