Is the same order on two rows of the Webpages report always double counting?

No. If the two rows belong to different conversion actions, that can be intentional multi-conversion measurement. Two rows with the same checkout token inside the same conversion action show one order counted twice; if the transaction IDs match Google Ads drops the second, if they do not both are counted.

What does the difference between a pixel sandbox URL and a plain checkout URL mean?

Shopify runs pixels inside a sandbox iframe, and Google Ads reads the conversion URL from the browser's location object. A conversion sent from a pixel therefore carries the sandbox URL, while one sent from theme code or a script carries the plain page URL. The URL pattern tells you which layer sent it.

Where do rows without a URL come from?

According to Google's list, iOS devices, modeled conversions, enhanced conversions, third-party integrations such as Shopify, and flows that use iframes can produce them. A conversion sent from a server or through an import has no page URL either; double counting from an external source is looked for in this group.

Does setting Count to One solve the problem?

No. One counts a single conversion per ad click; a customer who places two separate orders from the same click is also counted once. If the cause is an extra layer, the fix is removing that layer, and if two layers must both send the same order, deduplicating with a transaction ID.

Do conversions sent with the same key appear in the Webpages report?

I could not find a source documenting whether a conversion that Google Ads drops through the transaction ID still appears as a row in the Webpages report. When comparing row counts with unique token counts I therefore assume the report shows counted conversions; if evidence to the contrary turns up, the post will be updated.

Google Ads Conversion Double Counting on Shopify: Diagnosis with the Webpages Report and the Checkout Token

Whether the same Google Ads conversion is sent from more than one layer of a Shopify store can be read from the URL pattern in the Ads Webpages report and from the checkout token that is unique to each order, as long as the tag does not override the page URL itself. The post separates the pixel sandbox URL, the page URL and the external source the report never shows; it introduces Ads Goal Webpage Exporter, which writes the report to CSV with token and pixel columns, and matches each fix to its case.

TL;DR

The Google Ads Webpages report lists each conversion with the URL where it fired; Webpage unknown rows carry no URL and stay out. On Shopify the URL is the pixel sandbox pattern or the plain checkout path, both carrying the per-order checkout token. One token on several rows means several sources may have sent it. My Ads Goal Webpage Exporter extension writes the report to CSV with token and pixel columns; free, shared on request from a private repo.

Get Access Sign In

Subscribers Only

The full article plus 23 more subscriber-only posts come with a subscription.

analytics shopify google-ads

Subscribers Only

RELATED

Tracing the Source of GA4 and Ads Signals in Shopify

Joining Google Ads and GA4 at Row Level: A Shared Key and a Two-Layer Reading

Connecting a Shopify Order to an Ad Click: Choosing a Join Key for Offline Conversions

sGTM or Data Manager: The Wrong Question and the Right Distinction

Connecting a Backend Record to a Tag Conversion: Where the Uploaded Value Lands

Why Google Ads and GA4 Conversions Never Match: Counting Unit and Time Axis

Bridging Shopify Metafields and Custom Pixel: The Cart Attribute Pattern

Uploading with the Data Manager API: Setup Order from Authentication to Diagnostics

Writing the Same Conversion to Four Different APIs: Data Manager's Destination Map

Fractional Conversions in the Ads Dashboard: The Model or the Date Range?