> 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 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/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 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.
