> 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/what-would-you-like-to-learn-about/advocate-program/best-practices-for-referral-programs/convert-referrals-in-bulk-for-advocate.md).
# Convert Referrals in Bulk for Advocate
This guide shows how you can manually submit bulk conversions for referrals to an Advocate program.
{% stepper %}
{% step %}
#### Prepare your data
1. Create a file using the *file* *template* provided below.
2. Add your conversion data to the file using the *field reference* below.
3. Append any optional parameters you want to report as new columns in your file.
4. Save your file in .CSV format with an easily identifiable title and date (e.g., `2020-01-01_ConversionData.csv`).
**File template**
```
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
```
**Field reference**
| `CustomerId` | The email address of the referred user. |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `CustomerEmail` | The email address of the referred user. |
| `EventDate` | The date the order was placed in ISO 8601 format (recommended), or add `NOW` to use the current date. |
| `OrderId` | The unique order identifier. |
| `Amount` | The order total. |
| `EventTypeId` | Your 5-digit event type ID. |
| `CampaignId` | The 5-digit ID of the program where the event type was originally created.
- If the event type was created in your Performance program use the Performance program ID. The events will still make their way to your Advocate program.
|
| {% endstep %} | |
{% step %}
#### Submit your data file via email
1. In the top-right, select  **\[User profile] → Settings**.
2. Under the *Tracking* section, select [**Event Types**](https://app.impact.com/secure/advertiser/tracking-settings/actiontracker/view-actiontracker-flow.ihtml).
3. Hover over the event type, select  **\[More] → View / Edit**.
4. Select **Returns Processing**.
5. Select  **Automate Returns Processing (advanced).**
6. Then select  **Email file to system SMTP server** and copy your unique email address.
7. Using any email client, send an email to the unique address with your event data file as an attachment.
* Only include the unique email address in the `To:` field. If you need to send this file to others, include them in the `CC:` line.
* You can leave the subject field and message body blank.
{% 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/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.
