> 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/onsite-upsells.md).

# Onsite Upsells

### Onsite Upsell Metrics

This page is only available on tests that include an Onsite Upsell modification. When enabled, it can be accessed from the **View** dropdown in your test's analytics, and shows the following metrics for your onsite upsell widgets (PDP and cart), broken down by test group:

#### Upsell Metrics

* **Views:** Unique sessions in which an onsite upsell was shown.
* **Interactions:** Sessions with an onsite upsell interaction (hover, modal open, click to PDP, or add to cart).
* **Adds to Cart:** Sessions that added an onsite upsell product to cart.
* **Orders:** Number of orders containing an onsite upsell product.
* **Upsell CVR:** Orders with an onsite upsell divided by views — of the visitors who saw an upsell, the share who ordered one.
* **Revenue from Upsells:** Total net revenue generated by onsite upsells
* **AOV Lift:** Onsite upsell revenue per order — the portion of average order value driven by upsells.

Revenue and AOV figures follow the same accounting rules as the rest of Intelligems analytics — net of discounts, with refunded and canceled orders excluded. See more [here](https://docs.intelligems.io/analytics/overview/order-and-revenue-accounting.md).

#### Upsell Product Breakdown

This table shows stats on each product purchased through this upsell:

* **Offer:** The product that was purchased.
* **Test Group:** The test group the product was purchased in.
* **Units Sold:** Units of the upsell product sold.
* **Upsell Revenue:** Net revenue driven by this product.
* **Upsell Profit:** Net profit driven by this product.


---

# 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/onsite-upsells.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.