Revenue
/dashboard/<siteId>/revenue reads one kind of row: events that carried an
amount. Send one from the page where money changes hands and the screen fills
in. See Tracking revenue.
On a plan without Revenue the body is an upgrade panel instead. Past that, until the first revenue event arrives the screen is a Track revenue card with the two call forms and a copy button, rather than an empty dashboard. The revenue tile on Overview, the value column on Goals, the revenue line on a visit and the tile on a public dashboard stay hidden for the same reason.
Currency
Section titled “Currency”The screen reports one currency at a time. Adding a yen to a dollar produces a number that is true in no currency.
It opens on the site currency from Settings, or on the
currency that took the most money when the site currency took none. A
switcher appears at the top when more than one currency took money in the
range, listing each with its revenue and transaction count. ?currency=EUR
in the URL selects one directly.
Computed over the range, the current filters and the selected currency.
| Tile | Definition |
|---|---|
| Revenue | Sum of the amounts reported |
| Transactions | Count of revenue events |
| Average order | Revenue ÷ transactions |
| Customers | Distinct visitors who reported at least one amount. In cookieless mode a visitor is a browser-day, see How visitors are counted |
| Per visitor | Revenue ÷ unique visitors in the same filtered slice, so a country filter narrows both sides together |
Every tile carries a delta against the previous period of the same length.
Revenue per bucket, with transactions as a second series and the previous period drawn underneath for comparison. The bucket follows the range: hours for a day, days for a month, months for a year.
The running cumulative figure in the tooltip counts from the start of the requested range only. It is the shape of the period, not a lifetime total.
Breakdowns
Section titled “Breakdowns”Three panels, each with tabs. Every row reports revenue, transactions and customers, and every row is a link that filters the screen on that value.
| Panel | Tabs | Read from |
|---|---|---|
| What sold | Event, Page, Landing page | The event’s own name and path, and the first path of its visit |
| Acquisition | Source, UTM source, Medium, Campaign | The visit the event fired in |
| Audience | Country, Device, Browser | The visit the event fired in |
There is no “unattributed” row. A revenue event always has a visit, so it
always has a source, even when that source is Direct. See
How attribution works.
Transactions
Section titled “Transactions”Every revenue event in the range, newest first, twenty-five a page: the event
name, the page it fired on, the amount, the country and when. A row links to
the visit on Sessions, where the purchase sits in the
timeline with everything that led to it. ?page=2 in the URL walks the list.
Filters
Section titled “Filters”A dashboard filter describes visits. On this screen it keeps the revenue events whose visit matches, which is exactly the definition the visitor count on the same screen uses. Filtering never drops revenue from the total for any reason other than the filter itself.
URL parameters
Section titled “URL parameters”| Parameter | Values | Default |
|---|---|---|
range |
the nine range keys | 30d |
| all 26 filter keys | see Filters | none |
currency |
an ISO code that took money in range, case-insensitive | the site currency |
page |
integer ≥ 1, for the transaction list | 1 |