> 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/find-piggyback-pixel-user-permissions.md).
# 查找旁路像素用户权限
并非所有合作关系都可以使用 piggyback 像素。使用 piggyback 像素的权限在你的合作合同中设定，并且会因合作关系而异。
1. 从顶部导航栏中，选择 **发现 →** [**品牌**](https://app.impact.com/secure/mediapartner/marketplace/new-campaign-marketplace-flow.ihtml).
2. 选择你想查找其 piggyback 像素权限的品牌名称。
3. 在弹出面板的右侧栏中，选择 **详情** 选项卡。
4. 在 *我们的跟踪方式* 部分中，找到 *Pixel Piggyback* 模块。
* 如果模块上有绿色的  **\[检查]** 标记，你可以在此活动中使用 piggyback 像素。
* 如果该模块为灰色，则你不能在此活动中使用 piggyback 像素。
---
# 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/find-piggyback-pixel-user-permissions.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.
