> 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/zh/ni-xiang-liao-jie-shen-me/impactcom-mobile-app/mobile-app-reporting/performance-by-promo-code-report-on-the-mobile-app.md).
# 移动应用中的按促销码绩效报告
该 *按促销代码表现* 该报告向您展示了与您用于推广品牌的促销代码相关的特定跟踪数据。
## 管理报告
1. 从屏幕底部的导航栏中，选择  **\[报告]**.
2. 在 *报告* 部分中，选择 **按促销代码表现**.
3. 在右上角，选择日期  **\[下拉菜单]** 用于选择促销代码绩效数据的日期范围。
4. 在右上角，选择  **\[筛选]** 以筛选您要查看的数据。
* 详情请参见下面的 *筛选参考表* 如下。
筛选参考表
| 筛选 | 描述 |
| ---- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 排序方式 | 按……排序促销代码 *升序* 或 *降序* 按上线日期顺序，或按字母顺序。 |
| 品牌 | 通过选择相关的品牌，筛选与特定品牌相关的促销代码。  **\[复选框]**. |
5. 查看您的促销代码绩效数据明细。
* 详情请参见下面的 *报告数据列参考* 如下。
报告数据列参考
| 列 | 描述 |
| ---- | -------------------------------------------- |
| 总收益 | 查看您在所选日期范围内所选促销代码的总收入。这是所选计划中您所有促销代码的每日收入总和。 |
| 销售金额 | 这是您通过促销代码销售为合作品牌带来的总销售额。 |
| 操作 | 在所选日期范围内，您每个促销代码每次转化（销售、应用安装等）所获得的收益。 |
---
# 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/zh/ni-xiang-liao-jie-shen-me/impactcom-mobile-app/mobile-app-reporting/performance-by-promo-code-report-on-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.