Fix Shopify Google Ads Conversion Tracking Issues (Step-by-Step)

Fix Shopify Google Ads Conversion Tracking Issues (Step-by-Step)

Your Shopify store is receiving orders, but Google Ads shows no purchases. Or conversions are appearing, but every order has the same value. Sometimes the opposite happens: one customer order seems to generate two purchase conversions.

These problems can distort return on ad spend and give automated bidding the wrong signals.

The solution is not to install another tracking script immediately. First, identify where the measurement breaks: the checkout event, the tracking integration, the conversion action, or the report.

This guide walks through that process, including current Shopify pixel testing, duplicate tracking, consent, purchase values, and Google Ads attribution.

  1. Separate event collection from advertising attribution

A purchase appearing in Shopify does not automatically mean Google Ads should count an attributed conversion.

There are several separate stages:


Customer completes checkout
→ Shopify publishes the checkout event
→ The integration receives the event
→ Purchase data is sent to the intended Google destination
→ Google processes the event
→ Google determines attribution
→ The conversion appears in the relevant report

A failure or difference at any stage can produce missing or unexpected numbers.

For example, a direct-traffic test order can help demonstrate that a purchase event is sent. It does not, by itself, demonstrate that a campaign should receive conversion credit.

Likewise, a successful pixel callback is useful evidence, but it is not proof that the correct Google Ads conversion action received the correct value.

Treat these as separate checks.

  1. Identify which implementation owns purchase tracking

Before editing anything, document your existing setup.

Possible purchase-tracking paths include the Google & YouTube channel, a custom pixel, Google Tag Manager through a custom implementation, and GA4 purchase events imported into Google Ads.

Some stores have more than one.

Create a simple inventory:


Implementation:
Google & YouTube channel

Destination:
Google Ads account and conversion action

Purchase event:
Enabled or disabled

Additional purchase tracking:
Custom pixel, GTM, or GA4 import

Person responsible:
Merchant, developer, or agency

Connecting Merchant Center for product listings is not the same as configuring Google Ads conversion measurement.

Similarly, connecting a GA4 property is not, by itself, proof that the intended Google Ads purchase action has been configured.

My recommendation is to use the managed channel integration where it meets your requirements and reserve custom tracking for a defined need. Avoid maintaining several overlapping purchase implementations simply because each was added at a different time.

  1. Check the account connection and conversion action

For channel-based tracking, confirm that the intended Google Ads account is connected and that conversion tracking is enabled.

Then inspect the purchase conversion action in Google Ads.

Check its source, status, value settings, counting method, and whether your campaigns actually use its goal.

A working event can still be absent from the main campaign conversion column if the action is configured for observation rather than bidding.

Google distinguishes between:


Primary action:
Generally used for bidding and the Conversions column
when the campaign uses the associated goal.

Secondary action:
Generally reported in All conversions for observation.

There is an important exception: secondary actions included in a custom goal can be used for bidding when the campaign uses that custom goal.

Do not assume that changing an action to secondary always removes it from campaign optimization. Inspect campaign goals too.

  1. Test the Shopify checkout event

For an app pixel, use Shopify Pixel Helper to inspect events during a controlled checkout test.

The documented process is to select the app pixel’s Test option in Customer events, browse the store, and place a test order to inspect the Thank you page event.

For purchase tracking, the Shopify event is:


checkout_completed

The destination platform may call the corresponding event:


purchase

In Pixel Helper, a green dot indicates that the event subscription callback succeeded. A red dot indicates an error.

Record the result:


Checkout completed:
Yes

checkout_completed received:
Yes / No

Pixel callback:
Successful / Error

Consent state:
Recorded

Next check:
Google destination and payload

If the helper says the pixel is awaiting consent, provide consent through the test controls or the store’s banner to continue the consented test.

Do not permanently weaken privacy settings to make a test pass.

  1. Verify the Google destination, not just the event name

Next, inspect what the integration sends to Google using the diagnostic tools appropriate to that implementation.

Google Tag Assistant can help inspect Google tags and events. However, Shopify documents limitations with Tag Assistant for some migrated or sandboxed custom-pixel setups. An absent detection result is not automatically proof that every implementation is broken.

Check the intended destination identifiers and the specific purchase action.

For a custom Google Ads tag, this includes verifying that the conversion destination corresponds to the correct account and action, rather than an old agency account or a different event.

Keep your observations separate:


Shopify event:
Received successfully

Google purchase request:
Observed or not observed

Destination:
Matches intended action or does not match

Value and currency:
Correct or incorrect

Do not add a second Google tag merely because a diagnostic tool does not recognize the first one. First establish the implementation and its testing limitations.

  1. Audit legacy scripts and checkout migration

Older implementations may have placed tracking code in theme files, checkout customization code, or Additional scripts.

Shopify’s current pixel architecture uses app pixels or custom pixels for customer-event integrations.

A script appearing in the storefront theme does not establish that it measures checkout completion correctly.

During an audit, locate the old base tag and the old event code. Google tracking commonly includes references such as:


gtag(...)

or:


dataLayer.push(...)

These references are clues, not instructions to delete every matching line. A container or base tag may also support other measurement.

Plan the migration before removing anything. Shopify’s guidance recognizes the trade-off: overlapping implementations can duplicate events, while removing the old implementation before the new one works can create a measurement gap.

Use a low-traffic change window, preserve the previous configuration, and verify the replacement before declaring the migration complete.

  1. Fix duplicate purchase conversions

Duplicate tracking can happen in two different ways.

The first is duplicate event delivery to the same action:


One order
→ Managed integration sends purchase
→ Old custom script also sends purchase
→ Same conversion action receives both

The second is overlapping conversion actions:


One order
→ Direct Google Ads purchase action
→ GA4 purchase imported as another action
→ Both included in the campaign’s optimization setup

These require different fixes.

Google documents transaction-ID deduplication for repeated conversions within the same conversion action. Do not assume it automatically resolves two separate purchase actions.

For ordinary ecommerce measurement, choose a deliberate purchase action for optimization. Keep another source for comparison only if you have a clear reason, and verify primary, secondary, and custom-goal settings.

Do not delete conversion actions blindly. Preserve historical reporting and document the change.

  1. Use a stable, unique transaction ID

For custom implementations, purchase events should carry an appropriate transaction identifier.

The identifier must distinguish separate purchases while remaining consistent for repeat delivery of the same purchase.


Order A, first event:
ORDER-A

Order A, repeated event:
ORDER-A

Order B:
ORDER-B

Two common mistakes cause opposite problems.

A hard-coded identifier can suppress legitimate purchases because different orders look identical.

A newly generated random identifier on every page load can make repeated sends for the same purchase look different.

Google also explains that setting the counting method to “One” is not a substitute for transaction deduplication. It can count only one conversion after an ad interaction even when the customer makes multiple legitimate purchases.

Use transaction IDs to address repeated delivery, not a counting setting that hides valid sales.

  1. Diagnose incorrect purchase values

Start with one order you can inspect end to end.

Write down its merchandise value, discount, shipping, tax, currency, and final total. Then compare those components with the event payload and the conversion-action configuration.

An illustrative order:


Merchandise:
100.00

Discount:
10.00

Shipping:
5.00

Tax:
8.00

Final total:
103.00

A value of 90.00 and a value of 103.00 represent different definitions. Before calling one incorrect, establish which definition the integration is intended to send and which metric you are comparing.

Do not assume every managed integration includes or excludes the same components.

For custom tracking, investigate these common implementation errors:

  • A fixed value is configured instead of a transaction-specific value.
  • An amount in minor units is sent as a major-unit amount.
  • Formatted text is parsed incorrectly.
  • The pre-discount amount is used unintentionally.
  • Line quantities are multiplied twice.
  • The amount comes from a different currency than the supplied currency code.

Google’s transaction-specific value guidance requires a numeric value with a period as the decimal separator and an appropriate currency code.

This is an illustrative data shape, not a complete tracking implementation:


{
  value: 103.00,
  currency: "USD",
  transaction_id: "ORDER-A"
}

Do not copy it into production with static values.

  1. Check currency before comparing revenue

For international stores, inspect the amount and currency together.


Correct pairing:
103.00 USD

Incorrect pairing:
103.00 with an unrelated currency code

A numeric value without the correct currency can distort revenue reporting even when the purchase count looks reasonable.

Also distinguish the transaction currency from the Google Ads account’s reporting currency. Google documents currency conversion when transaction values are reported in a currency different from the account currency.

That means the number in the Ads report may not exactly match the original transaction amount.

For custom integrations, validate the raw monetary data rather than extracting a formatted amount from visible page text.

  1. Test consent and browser restrictions intentionally

Shopify web pixels respect the store’s customer privacy settings.

If a third-party consent banner does not sync its consent state through Shopify’s Customer Privacy API, pixels may remain blocked even after a shopper accepts tracking in that banner.

Test the relevant scenarios separately:


Before a consent choice:
Observe expected behavior.

After consent:
Confirm the permitted event flow.

After rejection:
Confirm the configured restrictions remain respected.

Do not hard-code consent as granted to make Google Ads numbers look closer to Shopify orders.

Browser privacy features and ad blockers can also reduce event delivery or attribution. Shopify documents that a pixel can send events while cookie restrictions still reduce the destination’s ability to connect them to an ad interaction.

Server-side measurement is not a blanket consent bypass either. Shopify’s server pixels remain subject to privacy and consent settings.

  1. Account for different purchase journeys

Not every Shopify order follows the same browser checkout journey.

For the channel’s browser purchase tracking, off-site payment is a useful test case. A customer can complete payment with an external provider but fail to return to the Thank you page.

Subscription renewals are another distinct case. The initial checkout purchase and an automatically generated renewal are not the same customer-event journey.

Separate these order types before diagnosing the gap:


Standard online checkout:
Test the complete purchase event flow.

External payment redirect:
Test payment and return to the store.

Initial subscription purchase:
Test the checkout event.

Automatic renewal:
Verify the subscription integration’s measurement approach.

Do not try to repair missing renewal measurement by making the storefront purchase event fire on unrelated page visits.

  1. Compare reports using aligned definitions

Even after tracking works, Shopify order totals, GA4 purchases, and Google Ads conversions do not necessarily match.

Compare the same date range, time zone, conversion action, currency, and purchase population.

Google Ads often reports conversion credit against the date of the ad interaction. An order report generally groups an order by when it occurred.

Google provides conversion-time reporting columns to help investigate that difference.

Also allow for processing time. Google’s data-freshness guidance varies by measurement source and attribution model, so a completed test purchase should not be judged solely by whether it appears instantly in a standard campaign report.

A useful comparison asks:


Did the event happen?
Was it sent correctly?
Was it processed?
Was it eligible for attribution?
Am I looking at the appropriate reporting column?

That is more useful than expecting every Shopify order to appear as a Google Ads purchase.

  1. Re-test with a small, documented test matrix

Before declaring the issue fixed, test representative cases.

  • A standard purchase.
  • A discounted purchase.
  • An order with shipping.
  • A transaction in another supported selling currency.
  • An external payment journey, if used.
  • A consented session.
  • A session with tracking declined.
  • A repeated visit to the confirmation experience, checking for unwanted duplicate sends.

For each case, record the purchase event, destination, transaction ID, value, currency, and observed errors.

Use an appropriate controlled testing process. Do not click your own live ads merely to manufacture attribution.

If the Shopify event fails, retain the pixel error and reproduction steps for investigation. If the event is sent correctly but the Google destination or reporting is wrong, provide that evidence to the integration provider or Google.

The recommended workflow

Start with one order and follow it through the measurement chain.

Confirm the checkout event, verify the destination, inspect value and currency, eliminate overlapping purchase tracking, and then evaluate attribution and reporting.

Do not install another script until you know which stage is failing.

Reliable conversion tracking means more than seeing a tag fire. It means the right purchase reaches the right action with the right value, without duplicate optimization signals.

Back to blog

Leave a comment