> 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/brand/zh/what-would-you-like-to-learn-about/advocate-program/best-practices-for-referral-programs/convert-referrals-in-bulk-for-advocate.md).
# 为 Advocate 批量转换推荐
本指南说明如何手动提交推荐到 Advocate 计划的批量转化。
{% stepper %}
{% step %}
#### 准备您的数据
1. 使用下方的 *文件* *模板* 如下所示。
2. 使用以下方式将你的转化数据添加到文件中， *字段参考* 如下所示。
3. 将您想要上报的任何可选参数作为新列追加到文件中。
4. 请以易于识别的标题和日期将文件保存为 .CSV 格式（例如， `2020-01-01_ConversionData.csv`).
**文件模板**
```
CampaignId,EventTypeId,CustomerEmail,CustomerId,OrderId,EventDate,Amount
XXXXX,XXXXX,bob@example.com,bob@example.com,12345-6,2026-02-17T18:43:39Z,188.29
XXXXX,XXXXX,friend@example.com,friend@example.com,12345-7,2026-02-17T18:43:39Z,215.53
```
**字段说明**
| `CustomerId` | 被推荐用户的电子邮件地址。 |
| --------------- | ------------------------------------------------------------------------------------------------------------------------- |
| `CustomerEmail` | 被推荐用户的电子邮件地址。 |
| `事件日期` | 订单下单日期，采用 ISO 8601 格式（推荐），或添加 `NOW` 来使用当前日期。 |
| `OrderId` | 唯一的订单标识符。 |
| `金额` | 订单总额。 |
| `EventTypeId` | 你的 5 位数事件类型 ID。 |
| `活动 ID` | 事件类型最初创建所在计划的 5 位数 ID。
- 如果事件类型是在你的 Performance 计划中创建的，请使用 Performance 计划 ID。事件仍会传递到你的 Advocate 计划。
|
| {% endstep %} | |
{% step %}
#### 通过电子邮件提交你的数据文件
1. 在右上角，选择  **\[用户资料] → 设置**.
2. 在 *跟踪* 部分下，选择 [**事件类型**](https://app.impact.com/secure/advertiser/tracking-settings/actiontracker/view-actiontracker-flow.ihtml).
3. 将鼠标悬停在事件类型上，选择  **\[更多] → 查看 / 编辑**.
4. 选择 **退货处理**.
5. 选择  **自动化退货处理（高级）。**
6. 然后选择  **将文件通过电子邮件发送到系统 SMTP 服务器** 并复制你的唯一电子邮件地址。
7. 使用任意电子邮件客户端，向该唯一地址发送一封电子邮件，并将你的事件数据文件作为附件。
* 只在 `收件人：` 字段中包含该事件类型的唯一电子邮件地址。如果你需要将此文件发送给其他人，请将他们包含在 `抄送：` 行中包含唯一电子邮件地址。
* 你可以将主题字段和邮件正文留空。
{% endstep %}
{% endstepper %}
---
# 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/brand/zh/what-would-you-like-to-learn-about/advocate-program/best-practices-for-referral-programs/convert-referrals-in-bulk-for-advocate.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.
