Google Ads purchase tracking for eCommerce
Make every Google Ads purchase signal mean one real order.
Verify the primary purchase action, transaction ID, dynamic value, currency and duplicate routes before using Google Ads reporting to make commercial decisions.
A tag firing successfully is not the same thing as reliable purchase measurement. The useful test is whether the intended reporting destination receives the right order, once, with the right value.
Start with a measurement contract
Define what a purchase means before inspecting tags.
The account should have one written definition of the purchase signal it is trying to optimise.
Document what counts as a purchase, which value is sent, which currency is used, how order identifiers are generated and how refunds are handled. The measurement contract should match the commercial questions the account is meant to answer.
Choose the purchase conversion action intended for bidding and keep secondary observations distinguishable from that primary signal. If a Google Ads website purchase and a GA4-imported purchase both exist, inspect how each is used before treating them as independent successes.
- What event counts as a purchase
- Which order value definition is sent
- Which currency belongs to that value
- How order IDs and refunds are handled
The fields to verify
Five checks decide whether the purchase signal is commercially useful.
Verify the final value received by the intended conversion action, not only the implementation layer that generated it.
Transaction ID
Use a stable, unique identifier for the real order and make sure it is present when the conversion fires.
Dynamic value
Send the agreed order-value definition, not a fixed placeholder or default value.
Currency
Send the correct currency for the value, especially when the store operates across markets.
Cart & product data
Where implemented, verify product identifiers, quantities and item values against the order.
Enhanced Conversions
Where appropriate, review implementation, data quality and applicable consent handling. Hashing does not replace consent or a correct tag.
Avoid false deduplication confidence
A transaction ID does not make every duplicate route disappear.
Google Ads uses transaction IDs to detect duplicate conversions within the same conversion action. Do not assume that the same 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 final count and value in the intended destination is the useful test.
Developer-ready test matrix
Test the purchase journey under normal and failure-prone conditions.
Record the expected result, observed result, timestamp and responsible owner for every test.
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 and 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.
Reconcile without pretending the systems are identical
Differences are expected. Broken measurement still needs investigation.
Store revenue, GA4 revenue and Google Ads attributed revenue do not need to match exactly because definitions and attribution can differ. Reconcile comparable periods and definitions first.
Investigate sudden changes in conversion count, repeated transaction IDs, fixed default values and currency mismatches before explaining every discrepancy as attribution.
Keep a test record with expected result, observed result, timestamp and responsible owner. Do not include customer names, email addresses or other personal information in a public diagnostic report.
Need this reviewed in your own account?
Find out whether measurement is the real acquisition constraint.
The €650 eCommerce Diagnostic reviews purchase measurement alongside Google Ads, Merchant Center, product data, economics and the store experience, then turns the evidence into a prioritised roadmap.
Continue the diagnosis
Put reliable purchase measurement back into the wider account.
Once the purchase signal is trustworthy, use the broader audit and order economics to decide what the account can actually afford.
41-point eCommerce checklist
Review economics, measurement, Merchant Center, feeds, campaigns, product pages and reporting.
Run the broader audit checklistBreak-even ROAS calculator
Turn representative order economics into break-even CPA, target CPA and target ROAS.
Calculate the order’s advertising allowanceeCommerce profitability guide
Connect measured purchase values to contribution, break-even limits and commercial decisions.
Evaluate contribution, not only revenueOfficial documentation
Check current Google documentation before implementation changes.
Platform features and requirements change. The source page references these Google Ads documents.
Trust the signal before scaling from it
Make purchase measurement reliable before asking Google Ads to optimise harder.
If transaction IDs, values, currencies or purchase routes are still unclear, the €650 eCommerce Diagnostic can turn the evidence into a prioritised action roadmap.