Skip to content

Andrei Visan · Google Ads for eCommerce

Google Ads Purchase Tracking for eCommerce

Check purchase actions, transaction IDs, value, currency and duplicate signals before using Google Ads reporting to make commercial decisions.

Make a purchase mean one real order

Start with a written measurement contract: what counts as a purchase, which value is sent, which currency is used, how order identifiers are generated and how refunds are handled. The contract should match the commercial questions the account is meant to answer.

Choose the purchase conversion action intended for bidding. Keep secondary observations distinguishable from that primary signal. If both a Google Ads website purchase and a GA4-imported purchase exist, inspect how they are used before treating both as independent successes.

The fields to verify

  • Transaction ID: a stable, unique identifier for the order, present when the conversion fires.
  • Dynamic value: the actual agreed order-value definition, not a fixed default.
  • Currency: the correct currency for that value, especially across markets.
  • Cart/product data where implemented: correct product identifiers, quantities and item values that reconcile with the order.
  • Enhanced Conversions where appropriate: review implementation, data quality and applicable consent handling. Hashing is not a substitute for consent or a correct tag.

Avoid false deduplication confidence

Google Ads uses transaction IDs to detect duplicate conversions within the same conversion action. Do not assume that an ID automatically deduplicates two separate primary purchase actions. Map every route by which the order enters reporting: native platform integration, Google tag, tag manager, GA4 import and server-side or offline sources.

A browser tag and a platform app can both appear healthy while measuring the same order twice. The test is the final count and value in the intended destination, not merely whether a tag fired.

A test matrix you can hand to a developer

Standard purchase

Place a controlled test order and record the transaction ID, value and currency. Verify the chosen destination action after normal processing.

Reload and return

Revisit the confirmation page and inspect whether a second event is sent and whether the conversion action deduplicates it.

Edge cases

Test discount codes, different currencies, shipping/tax treatment, consent choices and the supported checkout paths.

Refund or cancellation

Document whether conversion adjustments are supported and actually applied. Reconcile adjusted reporting against the store, allowing for reporting delays.

Reconciliation without pretending the systems are identical

Store revenue, GA4 revenue and Google Ads attributed revenue need not match exactly because definitions and attribution differ. Reconcile comparable periods and definitions first. Investigate sudden changes in count, repeated IDs, default values and currency mismatches before explaining every discrepancy as attribution.

Keep a test record containing expected result, observed result, timestamp and responsible owner. Do not include customer names, email addresses or other personal information in a public diagnostic report.

Continue the diagnosis

Want this reviewed in your own account? See the €650 eCommerce Diagnostic. For ongoing ownership, explore Google Ads Growth for eCommerce.

About the author

Written by Andrei Visan, a hands-on Google Ads consultant since 2010. The examples here explain a diagnostic method; they are not client performance claims.

Sources / Official documentation

Platform features and requirements change. Check the current documentation before implementing an account-specific change.