> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/reporting-and-performances/reporting/campaign-reporting/reporting-insights-with-evi-explore-powered-by-revenueiq/analysing-transaction-goals.md).

# Analysing transaction goals

Understanding the differences between risky and best practices is crucial

## Comparative metrics: risky practices vs. best practices

| **Decision making on**                     | **Risky practice (Based on metrics)** | **Best practice (Based on stats)**                      |
| ------------------------------------------ | ------------------------------------- | ------------------------------------------------------- |
| Revenue (with traffic perspective)         | RPU                                   | Revenue Uplift per user (revenueIQ)                     |
| Revenue (with business circle perspective) | Revenue uplift (potential)            | <p>Revenue Uplift per month<br>(RevenueIQ)</p>          |
| Revenue                                    | Revenue                               | Revenue Uplift Chance to win and confidence interval    |
| conversion                                 | Conversion rate growth                | Conversion uplift Chance To Win and confidence interval |
| Average Order Value                        | AOV growth                            | AOV uplift chance to win and confidence interval        |

## Managing variance in metrics for reliable decision-making

Using metrics for decision-making can be risky due to their inherent **variance**. Variance refers to the potential instability of data points, indicating that performance variations may not be consistent once deployed. The statistics provided by AB Tasty are specifically designed to minimize the noise caused by variance.

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.abtasty.com/reporting-and-performances/reporting/campaign-reporting/reporting-insights-with-evi-explore-powered-by-revenueiq/analysing-transaction-goals.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.