> 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-sub-id-and-shared-id-report-for-the-mobile-app.md).
# Performance by Sub ID & Shared ID Report for the Mobile App
The *Performance by Sub ID & Shared ID* report lists the programs where you've used tracking links with [Sub IDs or Shared IDs](/partner/what-would-you-like-to-learn-about/platform-features/tracking/tracking-links/link-parameters/sub-id-and-shared-id-parameters-explained-for-partners.md).
## Manage the report
1. From the navigation bar at the bottom of your screen, select  **\[Reports]**.
2. In the *Reports* section, select **Performance by Sub ID & Shared ID**.
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 brand names in alphabetical order for which you want to view sub ID data. |
| Brands | Filter for specific brands by selecting the relevant  **\[Check boxes]**. |
5. View a breakdown of your sub ID and shared ID 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
| Metric | Description |
| --------------- | ------------------------------------------------------------------------------------------- |
| Total Earnings | All commission earnings paid to you for the program. |
| Clicks | The number of times users followed your links to the brand's landing page. |
| Actions | The number of conversions you drove for the program, excluding any reversed by the brand. |
| RAW Clicks | The number of times users opened your link, including repeat clicks. |
| Impressions | The number of times your link was displayed for users to see. |
| RAW Impressions | The number of times your link was displayed for users to see, including repeat views. |
| Sale Amount | The total value of revenue you generated for the program. |
| Action Earnings | The amount of commission you received for driving the traffic that resulted in conversions. |
---
# 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-sub-id-and-shared-id-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.
