> 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/using-the-referring-url-parameter.md).

# 使用引用 URL 参数

<a href="https://pxa.impact.com/student/activity/1117597?sid=0c0e3e5c-54c9-4435-9bee-ebcdccb7f292&#x26;sid_i=0?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=tra-350&#x26;utm_campaign=help-center" class="button primary">参加 PXA 课程</a>

引荐 URL 是 [HTTP 引荐来源](https://en.wikipedia.org/wiki/HTTP_referer) 值，impact.com 会在用户点击时从其浏览器记录该值，因此它可以很好地反映访问您网站的流量来源。不过，它并非 100% 可信或可靠的跟踪来源，因为它在很大程度上取决于用户如何点击或打开链接。许多因素都可能影响发送给 impact.com 的引荐 URL。

#### 影响引荐 URL 可靠性的因素

如果您在 [*按引荐域名划分的效果*](https://app.impact.com/secure/advertiser/engage/additionalreports/report/viewReport.report?id=5243) 报告中看到点击记录的状态为“无引荐域名”，且该记录在 *域名* 列中，这通常表示没有可用的引荐 URL 信息，原因可能包括：

* 用户在浏览器地址栏中手动输入了网站 URL。
* 用户通过浏览器保存的书签访问了网站。
* 用户将该网站作为新窗口或新标签页中的第一个页面打开，例如右键点击链接。
* 用户点击了外部应用程序中的链接。
* 用户从安全协议 (https) 切换到了非安全协议 (http)。
* 用户从一个安全 URL (https) 切换到了完全不同的安全 URL (https)。
* 用户可能安装了会从所有请求中删除引荐来源信息的安全软件（防病毒软件、防火墙等）。
* 用户位于会从所有请求中删除引荐来源信息的代理服务器之后。
* 用户在未设置引荐来源标头的情况下通过程序访问了网站（例如，使用搜索机器人）。
* 某些浏览器的隐私政策会限制访问，以防止传递 `HTTP_REFERER` 。
* 用户安装了出于隐私原因拦截该信息的浏览器附加组件或扩展程序。

{% hint style="info" %}
**注意：** impact.com 建议您不要在支付组中使用“引荐 URL”选项来确定合作伙伴的付款，也不要过度依赖引荐 URL 作为决策数据来源。
{% endhint %}

<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-b3dac2d26258607a950b9584512ad5f86c1a701c%2F9e9ded014561edb602f4d45bb1a5ca1af1cffee80fc2c75e4ba595b98c4da955.png?alt=media" alt=""><figcaption></figcaption></figure></div>


---

# 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/using-the-referring-url-parameter.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.
