> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/partner/what-would-you-like-to-learn-about/impactcom-mobile-app/mobile-app-reporting/performance-by-day-report-for-the-mobile-app.md).
# Performance by Day Report for the Mobile App
The *Performance by Day* report lists your performance by day over a specified date range.
## Manage the report
1. From the navigation bar at the bottom of your screen, select  **\[Reports]**.
2. In the *Reports* section, select **Performance Day**.
3. In the upper-right corner, select the date  **\[Drop-down menu]** to select the date range of the performance data.
4. In the upper-right corner, select  **\[Filter]** to filter for the data you want to view.
* For details, see *Filter reference table* below.
Filter reference table
| Filter | Description |
| ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Sort By | Sort data by viewing it in *Ascending* or *Descending* order. |
| Brands | Filter for data associated with specific brands by selecting the relevant  **\[Check boxes]**. |
5. View a breakdown of your performance data. Select the  **\[Expand]** next to a day to open a detailed view of performance metrics.
* For details, see *Report data column reference* below.
Report data column reference
| Field | Description |
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Total Earnings | All commission earnings paid to you for that day. |
| Clicks | The number of times users followed your ad links to the brand's landing page. |
| Actions | The number of conversions you drove, excluding any reversed by the brand. |
| Sales Amount | The total value of revenue you generated for the brand. |
| Action Earnings | The amount of commission paid to you for the actions you drove. |
| EPA | The earnings per action represent the average monetary value you have earned from driving conversions. |
| EPC | The average amount of commission earned per click driven. |
| Conversion Rate | The conversion rate is calculated as the number of *Actions* divided by the number of *Clicks*, and it represents the percentage of clicks that result in conversions. |
| AOV | The average order value generated from your audience. This is calculated as revenue generated divided by the number of conversions (also known as actions). |
---
# 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://help.impact.com/partner/what-would-you-like-to-learn-about/impactcom-mobile-app/mobile-app-reporting/performance-by-day-report-for-the-mobile-app.md?ask=&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.