Skip to main content
Revenue analytics ties money to your traffic. Send revenue with a custom event, connect Stripe, or use both. tinyanalytics reports total and net revenue, refunds, average order value, paying sessions, orders, and acquisition breakdowns so you can see which traffic produces revenue.

​
Choose a revenue source

Add revenue and currency to any custom event you already send. These are reserved property names — tinyanalytics recognizes them and treats the event as a sale:
​
number | string
The amount in major units — dollars, euros, pounds — not cents. 49.99 means $49.99, not 49 cents. It accepts a number or a numeric string, and must be positive.
​
string
A 3-letter code like USD, EUR, or GBP (case-insensitive).
Only custom events carry client revenue. A pageview never does.
Send one event per completed sale. Client revenue must be positive, so this source cannot represent refunds or negative adjustments.
You can send the same event from your server with an API key. This is useful when the true paid moment occurs on your backend.

​
What does the Revenue report show?

Use the tabs at the top of the report to switch between All, Client events, and Stripe. The report includes these headline metrics: Below the metrics, a revenue-over-time chart shows the trend across your date range. A Revenue by table breaks revenue down across dimensions — channel, country, region, referrer, AI assistant, device, browser, operating system, and UTM tags.
Revenue in the breakdown is credited to the session’s entry acquisition — the source that first brought the visitor in. That means revenue-by-channel reconciles with sessions-by-channel: the channel that won the visit gets the credit for the sale, even if the purchase happened pages later.
tinyanalytics does not deduplicate the same purchase across client events and Stripe. If both sources report it, the All tab counts it twice. Choose one source of truth or use the source-specific tabs.

​
How does tinyanalytics convert currencies?

You can receive revenue in many currencies but read your reports in one. Set a reporting currency in your site’s general settings — the default is USD. Every amount is stored in the currency it was sent in, then converted to your reporting currency when a report is read. Conversion uses built-in exchange rates for 22 major currencies (USD, EUR, GBP, JPY, and the like), refreshed with each release. They’re approximate, not a live foreign-exchange feed. A valid currency code that isn’t in that set is stored and counted at a 1:1 rate rather than dropped, so no revenue ever goes missing. For exact multi-currency accounting, treat the reporting-currency total as a close estimate.

​
Where else does revenue appear?

Client revenue events power more than the Revenue report:
  • Goals — a revenue goal sums the money behind a conversion, not just its count.
  • Funnels — each step shows the revenue of the sessions that reached it.
  • Experiments — compare revenue and revenue-per-visitor across variants, counting only purchases after a visitor was exposed.
  • Alerts — get notified when revenue crosses a threshold you set.
These features currently read client events only; Stripe revenue is not included. Stripe data is available in the Revenue report and through scoped_stripe_revenue.

​
Frequently asked questions

Send it in major units — dollars, euros, or pounds — not cents. In tinyanalytics, a revenue value of 49.99 means $49.99, not 49 cents. The field accepts a number or a numeric string, and the amount must be positive.
Yes, through the Stripe integration. Stripe refunds and lost disputes subtract from net revenue. Client revenue events must remain positive and cannot represent refunds.
The revenue is stored and counted at a 1:1 rate rather than dropped, so no revenue goes missing. tinyanalytics has built-in rates for 22 major currencies (USD, EUR, GBP, JPY, and the like), refreshed with each release. For exact multi-currency accounting, treat the reporting-currency total as a close estimate.
The session’s entry acquisition — the source that first brought the visitor in. The channel that won the visit gets the credit, even if the purchase happened several pages later. This is why revenue-by-channel reconciles with sessions-by-channel.
tinyanalytics does not deduplicate the same purchase across client events and Stripe. If both sources report it, All counts both records. Use the Stripe or Client events tab as your source of truth, or stop sending the duplicate client event.

Track custom events

The events that carry revenue.

Goals

Turn a purchase into a revenue goal.

Funnels

See revenue at each step of a path.

Tracking API

Send revenue events from your server.

Connect Stripe

Receive verified payments and refunds.

Related topics

Stripe Revenue Analytics IntegrationAnalytics Metrics GlossaryAnalytics Site Settings