> 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/tracking-efficacy/causes-of-tracking-loss.md).

# 跟踪丢失的原因

追踪损失是通过以下差值计算得出的： *已发起的点击* （跟踪链接上的点击次数）和 *可归因点击数* （用户成功到达落地页的次数）。追踪损失有多种原因，其中一些可以识别并控制，另一些则是可以预期但仍应予以承认的。

该 [追踪效能报告](/brand/zh/what-would-you-like-to-learn-about/platform-features/tracking/tracking-efficacy/tracking-efficacy-report.md) 可为您提供有关您的计划中追踪损失的概览。

<details>

<summary>可控原因</summary>

| 原因      | 说明                                                                                                                                                |
| ------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| 广告拦截器   | 使用广告拦截器或隐私扩展的用户可能会阻止追踪标签，并防止其在其设备上加载，因此他们的活动无法被追踪。这一限制不适用于服务器端追踪方法，因为后者收集的是来自网站服务器的数据，而不是用户设备上的数据。                                                |
| 缺乏用户同意  | 越来越多的用户可以因隐私顾虑和法规要求而选择拒绝追踪。如果用户未提供追踪同意，就无法收集其数据，从而导致整体追踪数据出现缺口。对于已实施同意控制的地区，预计追踪效能会较低。请注意，在某些情况下，合作伙伴可能基于合法利益被追踪，而无需明确同意。请检查您是否在同意管理平台中考虑了合作伙伴类型。 |
| 追踪集成问题  | impact.com 集成的问题可能包括：标签加载缓慢、页面级错误、查询字符串参数的保留、标签实施问题，以及验证后的网站变更等其他可能性。                                                                             |
| 条件性执行追踪 | 如果您没有加载 UTT，或在每次通过 impact.com 追踪链接点击后到达的落地页上没有发出 Page Load API 请求，那么在落地页上有条件地执行追踪脚本可能会影响追踪效能分数。建议的实施方式是为所有用户在您网站/应用的所有页面上执行追踪。                    |

</details>

<details>

<summary>不可控原因</summary>

| 原因     | 说明                                                                                         |
| ------ | ------------------------------------------------------------------------------------------ |
| 跳出     | 当用户迅速离开，或从落地页“跳出”时，追踪标签可能没有足够时间加载并在用户离开页面之前捕获所需的用户数据。                                      |
| 非人工流量  | 无效点击可能由机器人生成——即旨在模仿人类行为的自动化程序，它们通常会产生虚假的展示和点击数据。impact.com 会过滤掉来自数据中心的部分点击，但更复杂的机器人可能仍会保留。 |
| 用户延迟问题 | 用户连接速度慢或服务器响应时间长都可能导致追踪问题。如果用户的连接很慢，追踪标签可能在他们离开页面之前都无法加载。                                  |

</details>


---

# 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/tracking-efficacy/causes-of-tracking-loss.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.