> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/analytics/overview/experiment-analytics/metric-definitions/revenue.md).

# Revenue

Within the Revenue tab, you will find:

#### Revenue Metrics

* **Revenue per Visitor:** Net revenue divided by number of unique visitors. Net revenue includes product and shipping revenue, net of discounts.
* **AOV (Average Order Value or Net Revenue per Order)**: Net revenue divided by number of orders.
* **Net Product Revenue per Order:** Product revenue, net of discounts. This generally does not include duties, fees, or taxes - see more [here](/analytics/overview/order-and-revenue-accounting.md#taxes-and-duties).
* **Net Shipping Revenue per Order:** Shipping revenue, net of discounts.
* **Average Units Per Order:** Total unit quantity divided by number of orders.
* **Average Product Revenue per Unit:** Net product revenue divided by unit quantity (i.e., average net price paid per unit).

Revenue data is up-to-date with the most recent updates to orders, including partial refunds, see more [here](/analytics/overview/order-and-revenue-accounting.md#partial-refunds-and-order-updates). Refunded and canceled orders are excluded, see more [here](/analytics/overview/order-and-revenue-accounting.md#refunds-and-cancellations).

#### Metric Details

This section provides statistical significance and time series for key revenue metrics.

#### By Audience

This section shows key revenue metrics by audience types.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intelligems.io/analytics/overview/experiment-analytics/metric-definitions/revenue.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.