> 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/de/was-mochten-sie-lernen/platform-features/tracking/piggyback-pixels/find-piggyback-pixel-user-permissions.md).
# Benutzerberechtigungen für Piggyback-Pixel finden
Nicht alle Partnerschaften können Piggyback-Pixel verwenden. Die Berechtigungen zur Verwendung von Piggyback-Pixeln werden in Ihrem Partnerschaftsvertrag festgelegt und können von Partnerschaft zu Partnerschaft variieren.
1. Wählen Sie in der oberen Navigationsleiste **Entdecken →** [**Marken**](https://app.impact.com/secure/mediapartner/marketplace/new-campaign-marketplace-flow.ihtml).
2. Wählen Sie den Namen der Marke aus, für die Sie die Berechtigungen für Piggyback-Pixel finden möchten.
3. Wählen Sie in der rechten Spalte des aufklappenden Bereichs die **Details** Registerkarte.
4. Im *So verfolgen wir* Bereich finden Sie *Pixel Piggyback* Block.
* Wenn sich ein grünes  **\[Check]** im Block befindet, können Sie für diese Kampagne Piggyback-Pixel verwenden.
* Wenn der Block ausgegraut ist, können Sie für diese Kampagne keine Piggyback-Pixel verwenden.
---
# 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/de/was-mochten-sie-lernen/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.
