> For the complete documentation index, see [llms.txt](https://docs.saferpay.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saferpay.com/home/interfaces/backoffice/transactions/myperformance.md).

# MyPerformance

{% hint style="warning" %}
**This feature is currently in open BETA testing.** It may not completely reflect all your transaction data yet. It is also currently only available in German and English.

The test-environment also uses dummy data and does not reflect your actual test input.
{% endhint %}

<figure><img src="/files/gdTttBE0mR4TvBDEtsQw" alt=""><figcaption></figcaption></figure>

This area gives you a wide array of analytical tools, to calculate your conversion rate, filter per payment method, rejection reason, payment type, currency, amounts, 3D Secure specifics and more. These can help to identify issues, optimize the payment experience for your customers, how well that new payment method is doing, or just to gain a general overview of well you are currently performing.


---

# 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.saferpay.com/home/interfaces/backoffice/transactions/myperformance.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.