How much of your revenue does Analytics actually measure?
Enter the figures from your shop system and from GA4 for the same period. The calculator compares order and revenue coverage and puts the result in a technical context.
Result
Order coverage
–
Revenue coverage
–
Unmeasured orders
–
Unmeasured revenue
–
Technical assessment
–
–
Recommended next step
–
These values describe the difference between the shop system and Analytics. Part of that difference is technically unavoidable: rejected consent, ad blockers, browser restrictions, order confirmations that never load, and platform processing. The shop system and Analytics will never match exactly.
Have the measurement gap reviewed technically
The Tracking Check documents which measurement paths send, which are duplicated and which are missing, and delivers an architecture decision with a fixed price.
About this calculator
Which figures do I need?
Orders and revenue from the shop system, plus purchase events and purchase revenue from GA4, each for the same period. A month is usually more meaningful than a week.
Why do the shop and GA4 never match exactly?
Rejected consent, ad blockers, browser restrictions, order confirmations that never finish loading, cancellations and the processing logic of the platforms always leave a residual difference. The question is not whether a difference exists but whether it can be explained.
Does the calculator show lost revenue?
No. It shows revenue that happened in the shop and is not visible in Analytics. That revenue is not lost, it is only unmeasured. The commercial damage is indirect, because campaigns and decisions rest on an incomplete picture.
What if GA4 counts more than the shop?
Then duplicate collection is very likely. Typical causes are a second measurement path, missing reload protection on the order confirmation, or a transaction ID that is not unique.
Are my inputs stored?
No. The calculation runs entirely in your browser. No values are sent to a server.