> 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/set-up-tracking/collect-campaign-data-with-google-analytics.md).
# 使用 Google Analytics 收集活动数据
您可以通过向所使用的目标 URL 添加活动参数来收集有关广告活动的信息。这样，您就可以跟踪不同社交媒体应用中的活动，也可以跟踪广告的电子邮件版或视频版。
当用户点击推荐链接时，您添加的参数会发送到 Google Analytics，相关数据可在 Google Analytics 的广告活动报告中查看。了解更多关于 [使用自定义 URL 收集活动数据](https://support.google.com/analytics/answer/1033863)  在 Google 的帮助中心。
1. 在顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 在右侧，在 *跟踪*，选择 **Gateway**.
* 了解更多关于 [配置网关跟踪设置](/brand/zh/what-would-you-like-to-learn-about/account-administration/program-settings/tracking-settings/configure-gateway-tracking-settings.md).
3. 在下方 *合作伙伴跟踪模板*，添加您希望自动附加到合作伙伴链接的 UTM 参数。请参阅 *参数参考* 下面了解可用参数的详细信息。
参数参考
共有 5 个参数 [可添加到您的 URL 中](/brand/zh/what-would-you-like-to-learn-about/account-administration/program-settings/tracking-settings/gateway-tracking-templates.md).
| 参数 | 说明 | Google Analytics 是否必需？ |
| -------------- | ------------------------------------------------------------------------------------ | ---------------------- |
| `utm_source` | 用于识别向您的资源发送流量的广告主、网站、出版物等，例如：impact.com、billboard。 | 是 |
| `utm_medium` | 广告或营销媒介，例如：cpc、横幅、电子邮件简报。 | 是 |
| `utm_campaign` | 单个活动名称、口号、促销代码等，用于某个产品。 | 是 |
| `utm_term` | 识别付费搜索关键字。如果您手动标记付费关键字活动，也应使用 `utm_term` 来指定关键字。 | 否 |
| `utm_content` | 用于区分同一广告中的链接。例如，如果您在同一封电子邮件中有两个行动号召链接，您可以使用 `utm_content` 并为每个链接设置不同的值，以便您区分点击了哪些链接。 | 否 |
4. 选择 **保存**.
#### 示例
Dunder Mifflin Paper Company 正在开展一项春季促销活动，他们使用以下参数来识别流量：
* `utm_campaign = spring-2024` 用于识别整个活动。
* `utm_source = spring2024-mailer` 用于识别由您的电子邮件活动产生的流量。
* `utm_medium = email` 用于识别来自电子邮件活动与应用内活动的流量。
您的自定义活动 URL 将为：
`https://www.example.com?utm_campaign=spring-2024s&utm_source=spring2024-mailer&utm_medium=email`
---
# 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/platform-features/tracking/set-up-tracking/collect-campaign-data-with-google-analytics.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.