Analytics dashboards often make two mistakes: they separate traffic from revenue so completely that the journey is hard to inspect, or they combine signals so aggressively that the numbers become difficult to defend.
We recently shipped a WebmasterID update designed around a different principle: show the available evidence together, but preserve the distinction between an observation and an authoritative conversion.
One geography model across Overview and Conversions
The new Geography panel is available in both Overview and Conversions. It can be switched between:
- events;
- active visitors;
- conversions;
- purchases;
- revenue.
This makes it possible to move from “where is activity coming from?” to “where are conversions and payments appearing?” without changing reporting tools.
The map does not infer precision the data source cannot provide. Country-level values use the available event or trusted edge context. Disputed territory is displayed as unassigned instead of being included in either claimant’s country geometry.
Supported conversions and Stripe payments in one workflow
The Conversions view now surfaces supported conversion types alongside Stripe webhook-verified payment events. That includes payment lifecycle events such as purchases, subscription starts, renewals, and refunds when the corresponding Stripe integration and webhook events are configured.
The important word is verified. A browser redirect to a success page is not proof that money moved. Stripe payment facts therefore come from signed webhook deliveries rather than DOM text, URL matching, or a client callback.
Keeping duplicate observations without double-counting revenue
A browser may observe that a checkout completed, and Stripe may later deliver the authoritative payment event. Throwing away the browser observation loses useful diagnostic evidence. Counting both inflates conversion and revenue metrics.
WebmasterID keeps those concerns separate:
- the observations remain inspectable;
- a canonical payment identity groups matching observations;
- only the counting record contributes to payment totals and revenue;
- evidence-only rows are labelled as such.
This gives operators visibility into the delivery path without turning retries or multiple reporting channels into extra revenue.
Multi-currency revenue stays multi-currency
The dashboard reports revenue separately by currency. It does not silently add unlike currencies into one total. A combined total would require an explicit exchange-rate source, valuation timestamp, and rounding policy; without those decisions, separate totals are the honest representation.
Identity is useful, but never invented
When a safe application identity or visitor link is available, recent conversions can connect a payment to the corresponding journey. When it is not available, the dashboard reports that identity was not provided. It does not select a nearby visitor because the amount and timestamp look similar.
The result is a conversion dashboard intended to answer not only “how many?” but also “why does this row count?”
You can explore WebmasterID at https://webmasterid.com/.
Top comments (0)