> 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 参数
参加 PXA 课程
引荐 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)。
* 用户可能安装了安全软件（防病毒软件、防火墙等），它会从所有请求中剥离引荐来源。
* 用户位于会从所有请求中剥离引荐来源的代理服务器之后。
* 用户是以程序化方式访问该网站的，且未设置 referrer 标头（搜索机器人所使用的方式）。
* 某些浏览器的隐私政策会限制访问，以防止 `HTTP_REFERER` 被传递。
* 用户安装了浏览器附加组件或扩展程序，出于隐私原因将其阻止。
{% hint style="info" %}
**注意：** impact.com 建议，在确定向合作伙伴支付款项时，不要在付款组中使用引荐 URL 选项，也不要过度依赖引荐 URL 作为决策的数据来源。
{% 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/using-the-referring-url-parameter.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.
