GA4 is installed—but can you trust the revenue number?

The monthly meeting opened with three versions of revenue. The order system reported 840 million tomans, GA4 was closer to 610 million, and advertising had a third number. Instead of making a decision, each team defended its own tool.

Test orders revealed that purchase depended on the thank-you page. Missing returns lost sales, refreshes duplicated others, and the data layer used value before discount. Three small implementation choices had made the dashboard impossible to trust.

Work backwards from a business decision

Do not collect every click by default. Write the decisions the team needs to make: which channel produces profitable customers, and where do shoppers abandon? Then define ownership, timing and parameters for view_item, add_to_cart, begin_checkout and purchase.

Product ID, name, currency, value and transaction_id must mean the same thing in the store, data layer and GA4. A minor identifier mismatch fragments product reporting.

Prevent duplicate purchases at the source

Refreshing a thank-you page can resend an event. Purchase should depend on a unique transaction ID and a confirmed order state—not merely a URL being opened.

Test failed payments, delayed returns and manually confirmed orders. The happy path is only a fraction of production behaviour.

Analytics is not accounting, but discrepancies must be explainable

Consent, ad blockers and timing create a normal gap. Still, reconcile order count and revenue with the order system every week and agree an alert threshold.

A concise tracking plan with events, parameters, firing locations and test cases is more valuable than a decorative dashboard because the next person can explain every number.

Pre-release quality checks

• Each event fires only at the correct moment.
• transaction_id is unique and persistent.
• Currency, value, discounts and tax have definitions.
• Mobile, desktop and failure paths are tested.
• A recurring reconciliation report exists.

Official reference: GA4 ecommerce event setup