Agree a common dictionary
Product view, add to cart, checkout start, purchase, cancellation and refund need separate definitions. Analytics, CMS and CRM use the same meanings.
Pass item composition
Ecommerce events include item_id, title, price, quantity, currency and other available parameters. The exact set depends on implementation; values are reconciled with the order.
Protect purchases from duplicates
One transaction_id represents one order. Reloading a page should not create another purchase. Test and cancelled orders are marked and excluded by an explicit rule.
Join systems by identifier
UTMs and ad IDs belong to a session; order_id to an order; client/user ID to permitted identification. Document joins and test data loss.
State the limit of the conclusion
The GA4 Ecommerce purchases report supports purchase analysis but does not replace accounting. Profit needs cost data; revenue is overstated without refunds; personal data requires an appropriate consent and legal basis.
Events and required evidence
| Event | Record | Source | Risk |
|---|---|---|---|
| view_item | Product and price | Website/app | Wrong item_id |
| add_to_cart | Item, quantity and value | Website/app | Duplicates on cart updates |
| begin_checkout | Basket and checkout stage | Checkout | Not a payment |
| purchase | transaction_id, value, currency, items | Order/payment | Repeated send |
| refund | Order, value and returned items | Order system | Revenue overstated without it |
Check before scaling
- price and availability agree across site and feed
- variants have stable identifiers
- purchase fires only after confirmation
- transaction_id survives reload without duplication
- refunds and cancellations are available to reporting
- margin is not calculated without reliable cost data
Short answers
Why do Ads and GA4 differ?
They use different attribution models, windows, consent states and processing times. Reconcile definitions and implementation before choosing a convenient number.
Can we optimise to add_to_cart?
It can be a temporary signal when purchases are sparse, but a cart does not become a sale. Document the decision and limitation.
Does ecommerce need a CRM?
It depends on order handling. CRM helps with assisted sales, wholesale and longer cycles; a standard purchase may use the order system as the primary source.
Need a system for your brief?
UMEDIA can map demand to a confirmed business status and scope the work without fabricated industry packages.
Send an enquirySources and review date
- Google Analytics: ecommerce events
- Google Analytics: Ecommerce purchases report
- Google Ads: product data
- Google Ads: Shopping ads
- Google Merchant Center: automatically added products
Sources were checked on 9 November 2026. The UMEDIA editorial team prepared this material with AI assistance and verified it against the official documents listed. It is a practical guide, not a client case or result guarantee.