> 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/set-up-general-tracking-settings.md).

# 设置常规跟踪设置

使用 *常规跟踪设置* 页面设置 impact.com 用于跟踪合作伙伴点击和转化的域名及跟踪选项。本文介绍该页面上的各项设置。

## 更改常规跟踪设置

{% stepper %}
{% step %}

### 前往设置页面

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. 在右侧的 *跟踪*下，选择 [**常规**](https://app.impact.com/secure/advertiser/fr/general-tracking-settings.ihtml).
   {% endstep %}

{% step %}

### 配置设置

使用下方各部分配置计划的设置。

{% hint style="warning" %}
**警告：** 更改这些设置可能会影响跟踪。如果不确定是否要更改这些设置，请阅读本文中列出的指南，或 [联系支持团队](https://help.impact.com/other/zh/reference-documentation/get-help-and-support.md).
{% endhint %}

1. “ *通用跟踪代码* ”是在网站上跟踪点击、会话和转化的脚本。选择 **复制代码** 以复制脚本。有关安装步骤，请参阅 [JavaScript 标签（UTT）](https://integrations.impact.com/integration-guides/for-brands/tracking-integrations/javascript-tag-utt).
2. “ *跟踪域名* ”字段显示跟踪链接使用的域名。若要使用自己的域名，请选择 **创建自定义跟踪域名**。有关设置步骤，请参阅 [设置自定义跟踪域名](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/set-up-tracking/set-up-a-custom-tracking-domain.md).
3. “ *站点定义* ”列表告知通用跟踪代码和页面加载 API 要跟踪哪些域名。请添加网站使用的所有域名和子域名，包括沙盒或测试站点。在 **站点定义** 字段中输入每个域名。请遵循以下规则：

   * 若要跟踪某个域名及其所有子域名，请输入根域名，例如 `acmecorp.com`.
   * 若只跟踪一个子域名，请输入完整的子域名，例如 `shop.acmecorp.com`。在这种情况下，跟踪不适用于 `www.acmecorp.com` 。
   * 如果客户的旅程经过多个域名，请将这些域名全部添加。

   若要允许合作伙伴深层链接到网站上的页面，请在 Gateway 设置页面添加相同的域名。详情请参阅 [设置深层链接的允许域名](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/account-administration/program-settings/tracking-settings/set-up-permitted-domains-for-deep-linking.md).
4. “ *URI 方案* ”字段用于指定此计划的统一资源标识符（URI）方案。页面加载 API 会使用该方案来确定应将流量关联到哪个计划。它还可以区分站内点击和来自网站外部的访问。如果有多个 URI 方案，请用逗号分隔。
5. 使用 *归因* 设置来控制 impact.com 如何跟踪计划的展示和点击。
   * 选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-b5e1740618ed6571d97b8fed7c25a7678f85d375%2F299632fb6f4f91fbf9847471754cc6180e4284a65b4960af4c4ea472a159f552.svg?alt=media) **\[未选中的复选框]** 以启用 **展示跟踪**，用于跟踪合作伙伴促销内容的浏览量。合作伙伴必须在其网站上添加 Impression Pixel 或 Publisher Tag。有关详情，请参阅 [Publisher Tag 常见问题](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/tracking-explained/publisher-tag-faq.md).
   * 选中 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-b5e1740618ed6571d97b8fed7c25a7678f85d375%2F299632fb6f4f91fbf9847471754cc6180e4284a65b4960af4c4ea472a159f552.svg?alt=media) **\[未选中的复选框]** 以启用 **跟踪来自计划外发布商的点击**，用于跟踪发布商在申请加入计划之前创建的跟踪链接所产生的点击。这些点击会显示在 [品牌方合作伙伴成效报告](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/performance-program/performance-program-reports/partner-productivity-report-for-brands.md)中，且不会影响计划归因。
   * 选中 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-b5e1740618ed6571d97b8fed7c25a7678f85d375%2F299632fb6f4f91fbf9847471754cc6180e4284a65b4960af4c4ea472a159f552.svg?alt=media) **\[未选中的复选框]** 以启用 **在落地页上接受 impact.com 点击参数**，用于根据落地页上的 URL（统一资源定位符）参数创建点击。此选项无需通过跟踪链接重定向，但需要集成落地页，例如 UTT、Page Load API 或兼容的电商集成。有关设置步骤，请参阅 [启用比价购物服务 (CSS) 合作伙伴跟踪](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/set-up-tracking/accept-clicks-on-landing-pages.md).
   * 落地页 URL 必须包含 `irmp` 参数。如果还包含 `irad` 参数，其值将成为该点击的广告 ID。比价购物服务合作伙伴通常会使用此选项。直接链接跟踪启用时，将优先使用直接链接跟踪。
   * 选择 **支持的 URL 参数** 以展开合作伙伴可以添加到落地页 URL 的参数列表。只有 `irmp` 是根据 URL 参数创建点击所必需的。其他参数均为可选参数；如果受支持，impact.com 会将其与点击一并保存。
6. 选中 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-b5e1740618ed6571d97b8fed7c25a7678f85d375%2F299632fb6f4f91fbf9847471754cc6180e4284a65b4960af4c4ea472a159f552.svg?alt=media) **\[未选中的复选框]** 以启用 **对所有模板条款启用暂停政策**，表示您遵循暂停政策。有关详情，请参阅 [暂停政策说明](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/stand-down-policy-explained.md)。这能让合作伙伴更有机会继续保持转化“胜出者”身份。如果您不遵循暂停政策，请取消选中此框。
7. 选择 **连接 Segment 账户** 以将 Segment 流量添加到您的 impact.com 账户。有关设置步骤，请参阅 [与 Segment 集成](https://integrations.impact.com/integration-guides/for-brands/plugin-integrations/cdp-customer-data-platform/integrate-with-segment).
8. 选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FiZjM1xY8o3v1iR3Zaysd%2FToggle.svg?alt=media\&token=b1550d48-bba9-4e81-8604-bc12370c5caa) **\[开关已开启]** 以开启身份匹配，或选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FACIoqj1Ayhx8QzL9aqYB%2Ftoggle-off-solid%20\(1\).svg?alt=media\&token=a85366cd-4b70-41a6-83df-319f89597ede) **\[开关已关闭]** 以将其关闭。身份匹配可启用跨设备归因。开启后，请选择以下选项之一：

   * 选择 **仅针对计划选择加入** 以仅在此计划内匹配身份。
   * 选择 **选择加入 impact.com 联盟** 以在 impact.com 平台范围内扩展匹配，从而更全面地了解客户旅程。有关详情，请参阅 [选择加入 impact.com 联盟](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/cross-channel-performance-insights/opt-in-to-the-impactcom-consortium.md).

   要进行计划级匹配，您需要额外的标识符，例如 `CustomerId` 或 `CustomerEmail`.
9. 选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-b5e1740618ed6571d97b8fed7c25a7678f85d375%2F299632fb6f4f91fbf9847471754cc6180e4284a65b4960af4c4ea472a159f552.svg?alt=media) **\[未选中的复选框]** 以启用 **使用 LiveRamp 集成**，启用后即可进行 LiveRamp Cookie 同步。启用后，您网站每位访客对应的 impact.com Cookie 都会与相应的 LiveRamp Cookie 匹配。任何 LiveRamp 使用场景（例如离线数据导入或 Segment 报告）都需要启用此功能。
   {% endstep %}

{% step %}

### 保存

选择 **保存** 以保存更改。
{% endstep %}
{% endstepper %}

## 更多资源

* [设置自定义跟踪域名](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/set-up-tracking/set-up-a-custom-tracking-domain.md)：创建自己的跟踪域名，让跟踪链接使用您的品牌域名。
* [确定您的计划是否符合 ITP 要求](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/set-up-tracking/determine-your-programs-itp-compliance.md)：检查您的跟踪域名是否适用于 Safari 的智能跟踪预防功能。
* [配置 Gateway 跟踪设置](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/account-administration/program-settings/tracking-settings/configure-gateway-tracking-settings.md)：为您的计划设置 Gateway。
* [设置深度链接的许可域名](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/account-administration/program-settings/tracking-settings/set-up-permitted-domains-for-deep-linking.md)：选择合作伙伴可在您的网站上深度链接到哪些域名。


---

# 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/set-up-tracking/set-up-general-tracking-settings.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.
