> 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="https://3537448238-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fzpi9teY7Tm2pCZ1Bw8zO%2Fuploads%2FLtyFVsWGjPJF8Efg4hnv%2FBO_MyPerformance.png?alt=media&amp;token=d0486ade-b61c-4845-808d-b35839a92dfb" 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, determine how well that new payment method is doing, or just to gain a general overview of how 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 by asking a question.

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

```
GET https://docs.saferpay.com/home/interfaces/backoffice/transactions/myperformance.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.