> 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/tracking/mobile-app-tracking/mobile-tracking-using-mmps-explained.md).

# 使用 MMP 进行移动跟踪说明

移动测量合作伙伴（MMP）是第三方工具，可帮助品牌更好地了解其移动应用营销项目的表现。如果您使用 MMP 并希望推动应用内转化，您可以将 MMP 与 impact.com 集成，在一个便捷的位置跟踪、报告并为移动应用事件进行结算。

#### MMP 跟踪是如何工作的？

MMP 会跟踪、归因并整理来自各个渠道的数据。当客户点击这些渠道中的某个链接时，链接会通过 MMP 重定向，MMP 会存储有关该点击的数据。如果客户之后完成了转化，例如安装了品牌的移动应用，MMP 会将该转化数据与最初的点击相匹配，并将功劳归因到正确的来源，从而使品牌能够在未来做出战略性的预算决策。

当您将 MMP 与 impact.com 集成时，您可以将某些跟踪参数传递到您的 impact.com 账户，包括 `ClickId`。这使您能够将 MMP 的功能与 impact.com 的报告、财务和扩展跟踪功能结合起来。

#### 前提条件

* 您正在使用一个 [impact.com 支持的 MMP](#which-mmp-integrations-are-supported).
* 您的 MMP 具备您正在使用或预计将用于向合作伙伴付款的所有必需参数。

#### 支持哪些 MMP 集成？

* [Adjust](https://integrations.impact.com/integration-guides/for-brands/plugin-integrations/mmp-mobile-measurement/integrate-with-adjust)
* [AppsFlyer](https://integrations.impact.com/integration-guides/for-brands/plugin-integrations/mmp-mobile-measurement/integrate-with-appsflyer)
* [Branch](https://integrations.impact.com/integration-guides/for-brands/plugin-integrations/mmp-mobile-measurement/integrate-with-branch)
* [细分](https://integrations.impact.com/integration-guides/for-brands/plugin-integrations/cdp-customer-data-platform/integrate-with-segment)
* Kochava（要了解更多信息， [联系支持团队](https://app.impact.com/support/portal.ihtml).)


---

# 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/tracking/mobile-app-tracking/mobile-tracking-using-mmps-explained.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.