> 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/configure-custom-uri-schemes.md).

# 配置自定义 URI 方案

**URI 方案**，它们显示在 URL 的协议部分，用于向 *客户端*（例如 Web 浏览器）指示如何解读 URL 协议之后的所有内容（即协议后面的 `://`）。如果您使用 impact.com 的 Page Load API 并希望使用自定义 URI 方案，则需要在 impact.com 的 Web 应用中列出要传递的方案。

<div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-50500e0c05347cae50075039e1c285bf18146af6%2F0d4703b4888e1b0b4ec339fe76c47848126a700c321274e9c50fc56f09221ea1.png?alt=media" alt=""><figcaption></figcaption></figure></div>

impact.com 使用这些 URI 方案来确保流量关联到正确的计划，并区分网页之间的站内点击与新流量或引荐流量。不过，如果未列出要使用的方案，Page Load API 可能会对包含自定义 URI 方案的 URL 返回错误，或者 impact.com 可能会直接拒绝这些 URL。

如果您打算在计划中使用 [直接流量跟踪](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/set-up-tracking/set-up-direct-traffic-tracking.md) ，也应考虑列出自定义 URI 方案。

#### 列出 URI 方案

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. 在右侧的 *跟踪*下，选择 **常规**.
3. 在 *URI 方案*中，输入您打算传递的自定义 URI 方案。各个值之间用逗号分隔。
4. 选择 **保存**.

   <div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FHbgAfZPbR0HnZhksGX7P%2FScreenshot%202026-05-06%20at%2012.03.17.png?alt=media&amp;token=f9cbe6f3-5feb-4fe1-bb9d-cc86ea6b762c" alt="" width="338"><figcaption></figcaption></figure></div>

PayPal 等支付网关网站会自动视为站内流量，无需手动添加。

{% hint style="info" %}
**注意**：impact.com 不接受非 HTTP 风格的 URI 方案（例如 `file` 或 `mailto`).
{% endhint %}


---

# 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/configure-custom-uri-schemes.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.
