Analytics you can actually trust

Conversion and growth 8 min read

A monitor showing two charts that disagree, with a notebook of hand tallies beside it
Two systems, two answers. Reconcile before you decide.

Every store eventually discovers that its analytics revenue and its actual revenue do not match. Consent choices, ad blockers, refunds, failed payments and duplicated events all pull in different directions, and the gap is often twenty percent or more.

That gap does not make analytics useless. It makes reconciliation the first job, because decisions taken on unreconciled numbers are guesses wearing a chart.

Why the numbers disagree#

Analytics you can actually trust — Why the numbers disagree
CauseDirectionWhat to do
Consent declined or blocked scriptsUndercountsMeasure the gap, do not pretend it is zero
Duplicate purchase eventsOvercountsFire once, keyed on order id
Refunds and cancellationsOvercounts revenueReconcile against the order table monthly
Failed payments counted as ordersOvercountsOnly count on confirmed payment
Cross-device journeysMisattributesAccept the limit; prefer directional reading

The three numbers worth trusting#

  1. Orders and revenue from your own database. This is the truth other systems approximate.
  2. Step-by-step funnel counts from your own instrumentation, used for direction rather than absolute value.
  3. Server-side conversion events keyed on order id, so refunds and duplicates can be corrected.

Set up the reconciliation once#

Monthly, compare analytics revenue with order-table revenue net of refunds, and record the ratio. A stable ratio means you can read trends confidently. A moving ratio means something changed in the tracking, not in the business.

That single ratio prevents most of the panicked meetings about a sudden drop that never happened.

What to stop measuring#

Vanity metrics that no decision depends on. If nobody can name the action a number would trigger, remove it from the dashboard — every metric on screen competes for the attention of the ones that matter.

Frequently asked questions

Should I move to server-side tracking?

For purchases, yes. It survives blockers and lets you key events on order id.

How big a gap is normal?

Ten to thirty percent depending on market and consent rates. Measure yours rather than assuming.

Which number do I report to the business?

The order table, net of refunds. Analytics explains where it came from.

ecommerce analyticstracking accuracyserver side trackingrevenue reconciliationfunnel measurement

All guides

Last updated 2026-08-05 by ecommercedevelopment.info · About us

Written by builders

Every guide is written by developers who ship and maintain real stores, not spun from other sites.

Reviewed on a schedule

Platforms and payment rules change. Each guide carries the date of its last review, and we publish the date even when nothing changed.

No paid placements

No platform, theme shop, app vendor or agency can buy a mention, a ranking or a link here.

Twelve languages

Every guide is translated, not machine-popped — each language has its own URL and its own review date.

Limits named

We say plainly when a hosted platform or a marketplace listing would be cheaper and more reliable than a custom build.