> 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/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/tracking/piggyback-pixels/test-piggyback-pixels.md).

# 测试旁路像素

测试 piggyback pixel 可确保您的第三方跟踪系统能够正确接收来自 impact.com 的转化数据。本文将指导您如何为特定品牌定位并测试 piggyback pixel，验证其是否正确触发，并确认转化是否正被端到端跟踪。无论您是品牌方、创作者还是直接合作伙伴，遵循这些步骤都有助于验证您的像素设置，并保持准确的绩效跟踪。

1. 在顶部导航栏中，选择 **发现 →** [**品牌**](https://app.impact.com/secure/mediapartner/marketplace/new-campaign-marketplace-flow.ihtml).
2. 选择您想测试 piggyback pixel 的品牌。
3. 在该品牌的侧边展开菜单中，选择 ![](https://1152657667-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2Fgit-blob-8ec3e877b1397045c61d394485e72ac4d93120ee%2Fc6ddb46c637059f06e86c790a911217a9428f5c47b5efef046f90555e85b03cd.svg?alt=media) **\[更多]** → **跟踪集成**.
4. 在 *媒体合作伙伴跟踪像素* 表格中，找到要测试的 piggyback pixel，然后在 *操作* 列中，选择 ![](https://1152657667-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2Fgit-blob-df93ac0f80fc5cece7983980a5ce3fbcf19aabce%2F3ef9d737089bc07dbb7e4fd41a97edfbaec261e4f55ab3a1666f3daf957f69c3.svg?alt=media) **\[下拉菜单]** → **测试**.
5. 在新窗口中，输入落地页 URL 并选择 **启动测试**.
6. 您将被重定向到一个包含两个选项的页面。
   * 如果内部跟踪测试 URL 已正确设置，您将被带到所测试活动的落地页。选择 **触发转化 piggyback**，随后 impact.com 将调用该像素，这将在您的第三方跟踪系统中显示为一次转化。
   * 继续完成该品牌的转化流程，并进行端到端测试。这将在您的第三方系统中显示为一笔交易，并在 Impact 中显示为一个待处理操作。


---

# 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/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/tracking/piggyback-pixels/test-piggyback-pixels.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.