> 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
```
**字段说明**
| `客户ID` | 被推荐用户的电子邮件地址。 |
| ------------- | -------------------------------------------------------------------------------------------------------------------------- |
| `客户邮箱` | 被推荐用户的电子邮件地址。 |
| `事件日期` | 订单下达日期，采用 ISO 8601 格式（推荐），或者添加 `NOW` 以使用当前日期。 |
| `订单ID` | 唯一的订单标识符。 |
| `金额` | 订单总额。 |
| `事件类型ID` | 您的 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
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 optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.