eCommerce purchase measurement
Google Ads purchase tracking: verify one real order end to end.
Check the primary purchase action, unique transaction ID, dynamic value, currency and duplicate routes. Validate what reaches the intended reporting destination, not just whether a tag fires.
Test the intended conversion action, count and value.
Purchase measurement
Verify the intended signal at the reporting destination.
Write down what a purchase means.
Define the event that counts as a purchase, which order value is sent, the relevant currency, how transaction IDs are generated and how refunds are handled. Identify the purchase action intended for bidding and distinguish secondary observations.
If both a Google Ads website purchase and a GA4-imported purchase exist, review their bidding use before treating them as separate successes.
Verify the fields received by the destination.
Transaction ID
Use a stable identifier unique to each real order. Confirm it is populated at the moment the conversion is sent.
Dynamic value and currency
Send the agreed order-value definition and correct currency. Avoid fixed defaults and check market-specific checkout paths.
Items and enhanced conversions
Where implemented, compare product IDs, quantities and item values with the order. Review enhanced-conversion data quality and applicable consent handling. Hashing does not replace correct setup.
A transaction ID does not resolve every duplicate route.
Google Ads uses matching transaction IDs to recognise duplicates within the same conversion action. Do not assume that two separate primary purchase actions automatically deduplicate each other.
Map every route: native platform app, Google tag, tag manager, GA4 import and any server-side or offline source. A browser tag and a platform integration can each fire successfully while creating the wrong total. Verify the final conversion count, value and bidding use.
Use an end-to-end test record.
| Test | What to verify |
|---|---|
| Controlled purchase | Record expected order ID, value and currency; confirm the intended conversion arrives once after processing. |
| Reload and return | Revisit confirmation and check whether another event is sent and how the destination handles it. |
| Checkout edge cases | Test discounts, currencies, shipping/tax treatment, consent choices and supported payment paths. |
| Refund or cancellation | Document whether adjustments are supported and actually applied; allow for reporting delays. |
Reconcile comparable views.
Store revenue, GA4 revenue and Google Ads attributed revenue can differ because their definitions and attribution differ. Compare consistent periods and bases first.
Investigate repeated IDs, default values, sudden count changes and currency mismatches before explaining every discrepancy as attribution. Measurement should support the commercial questions, rather than simply produce more events.
Put measurement into the wider review.
Official documentation.
Use the current platform guidance when planning implementation changes.
Need to decide what to fix first?
The €650 eCommerce Diagnostic reviews the wider account and turns the evidence into a prioritised roadmap and review call. Ongoing management is scoped around catalogue, markets and implementation needs.
Written by Andrei Visan.
I’ve worked hands-on with Google Ads since 2010. This resource explains a diagnostic approach, not a claim of specific client results.
Find the next useful account action.
Bring the store and the acquisition problem. We can confirm whether the €650 diagnostic or another next step fits.