> 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/platform-features/submit-and-modify-conversion-data/batch-modify-conversion-data/mobile-specific-parameters-for-ftp-or-email-conversion-reporting.md).

# FTP 或电子邮件转化报告的移动专用参数

<a href="https://pxa.impact.com/student/activity/1117597?sid=0c0e3e5c-54c9-4435-9bee-ebcdccb7f292&#x26;sid_i=0?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=tra-350&#x26;utm_campaign=help-center" class="button primary">参加 PXA 课程</a>

在你的移动应用中发生的转化可以像标准网页转化一样，通过 FTP 或电子邮件以 CSV 文件提交到 impact.com。本文将向你展示如何在 impact.com 中查找你的移动应用标识符，这些标识符在创建 CSV 文件时会用到，以及你可以在该文件中包含的移动端专属参数。

与标准网页转化报告的主要区别在于获取 *System App ID* 和 *事件代码* 值——在提交要由你的移动应用跟踪的转化时需要这些值。该 *System App ID* 值会作为 `ActionTrackerID` 你 CSV 文件中的值。

impact.com 建议在可用时提交这些移动端专属参数——它们有助于更准确的归因，并扩展报告中可用的数据。

#### 查找你的 System App ID 和 Event Code 值

1. 从顶部导航栏中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2F210dEQa93qyQgoJDkieL%2FUser%20profile.svg?alt=media\&token=f84c5b17-fae4-4a30-990a-9de5e57a150b) **\[用户资料] → 设置**.
2. 在右侧列中，位于 *跟踪*，选择 **移动应用**.

   * 请记下位于 *System App ID* 你的移动应用对应列中的值。这些值会作为 `ActionTrackerId` 你 CSV 文件中的

   <div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FkLpKn3Efnivby6bOIFuY%2FScreenshot%202026-05-06%20at%2018.54.44.png?alt=media&amp;token=08961bff-66f7-4e71-94e0-edf9cd91d01a" alt="" width="563"><figcaption></figcaption></figure></div>
3. 将鼠标悬停在该应用上，然后选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FMLtRUwWz0pujlfmYWOgg%2FMoreVN.svg?alt=media\&token=03a3c355-a347-4207-baf7-c44fadf6d080) **\[更多]** **→ 管理事件**.
   * 请记下位于 *事件代码* 列中的值。这些值会作为 `EventCode` 你 CSV 文件中的

#### 移动端专属参数

{% hint style="info" %}
**注意：** 以下列出的参数 *是对* 提交转化的标准参数（例如， `ClickId`, `CustomerId`）的补充。请参阅 [通过 FTP 或电子邮件提交转化数据](/brand/zh/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/submit-conversion-data/submit-conversion-data-via-ftp-or-email.md) 以了解创建 CSV 文件并将其提交到 impact.com 的流程。
{% endhint %}

<details>

<summary>参数参考表</summary>

| **参数**          | 必填/可选              | 说明                                                                                                        |
| --------------- | ------------------ | --------------------------------------------------------------------------------------------------------- |
| `EventCode`     | **提交移动端转化时必填**     | 你想要报告的、在移动应用中发生的事件的自定义标识符（例如， `INSTALL`).                                                                 |
| `GoogleAid`     | **必填，除非提供了其他归因来源** | 与客户完成转化时所用移动设备关联的 Google Advertising ID。用于归因目的。通常仅适用于 Android 应用内转化。                                      |
| `AppleIfa`      | **必填，除非提供了其他归因来源** | 与客户完成转化时所用移动设备关联的 Apple ID for Advertising（IDFA）。用于归因目的。通常仅适用于 iOS 应用内转化。                                 |
| `AppleIfv`      | **必填，除非提供了其他归因来源** | 与客户完成转化时所用移动设备关联的 Apple ID for Vendors（IDFV）。用于归因目的。通常仅适用于 iOS 应用内转化。                                     |
| `AppPackage`    | 可选                 | 用户安装的移动应用的软件包名称。                                                                                          |
| `AppVer`        | 可选                 | 移动应用的版本。仅适用于移动端转化。                                                                                        |
| `AppInstallRef` | 可选                 | 仅适用于 Android 转化。应用安装时由 Google Play 商店传递的安装 referrer。通常，来自 impact.com 跟踪链接传递的值将是 `clickid={clickidvalue}`. |
| `DeviceMfr`     | 可选                 | 主要用于移动端应用内转化，这是用户完成转化所用设备的制造商。                                                                            |
| `DeviceModel`   | 可选                 | 用户完成转化所用设备的型号。如果转化是通过网页完成的，则会根据传入的用户代理自动确定该值。                                                             |
| `DeviceCarrier` | 可选                 | 移动设备的运营商。                                                                                                 |
| `DeviceOs`      | 可选                 | 移动设备的操作系统。                                                                                                |
| `DeviceOsVer`   | 可选                 | 可选。                                                                                                       |

</details>

#### 示例 CSV

```programlisting
CampaignId,ActiontrackerID,EventCode,EventDate,OrderId,ClickId,Amount,Category,Sku,Quantity,AppleIfa,AppleIfv,AppPackage,AppVer,DeviceModel,DeviceOsVer
1000,8882,INSTALL,2038-01-19T03:14:07-00:00,T52324111211,QiiWXOVnrQ3SQHl24jQjyxBGUkmzfJ3i1VHrWM0,0,,,1,EA7583CD-A667-48BC-B806-42ECB2B48606,EA7583CD-A667-48BC-B806-42ECB2B48607,com.example.myapp,10.0.1,iPhone 12,14.4
```


---

# 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/platform-features/submit-and-modify-conversion-data/batch-modify-conversion-data/mobile-specific-parameters-for-ftp-or-email-conversion-reporting.md?ask=<question>&goal=<user_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.