> 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/enable-cross-program-tracking.md).
# 启用跨项目跟踪
参加 PXA 课程
如果您有多个项目，可以启用跨项目跟踪，使由一个项目产生的点击也可被视为您其他项目的有效推荐。这在您拥有彼此互相链接的不同网站时很有帮助。例如，如果您有两个关系密切的品牌，且两者之间导航方便，即使客户的转化发生在另一个网站，您也可以将流量导入其中一个网站的功劳归于某个合作伙伴。
为了让跨项目跟踪有效运行，您的合作伙伴必须在所有相关项目中都拥有有效合同。在审核合作伙伴申请时，您可以选择 **接受所有项目**。然后，合作伙伴将通过您的默认模板条款加入您的其他项目。
#### 启用跨项目跟踪
{% hint style="warning" %}
**重要：** 创作者项目中不应启用跨项目跟踪，因为这会干扰跟踪和归因。
{% endhint %}
1. 在顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 从 *技术* 左侧部分中，选择 **跨项目跟踪**.
3. 在 *跨项目跟踪* 屏幕上，打开 **允许在我的项目之间跟踪**，然后在两个跨项目跟踪选项中进行选择：
* *我的所有项目*—跟踪您所有项目之间的流量。
* *特定项目*—指定要在哪些项目之间跟踪流量。
* 选择特定项目时，请使用  **【Command】** 或  **【Control】** 键选择多个项目。
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 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/enable-cross-program-tracking.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.
