> 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/what-would-you-like-to-learn-about/platform-features/tracking/piggyback-pixels/find-piggyback-pixel-user-permissions.md).

# Find Piggyback Pixel User Permissions

Not all partnerships can use piggyback pixels. Permissions to use piggyback pixels are set in your partnership contract, and can vary from partnership to partnership.

1. From the top navigation bar, select **Discover → My Brands**.
2. Select the name of the brand you want to find piggyback pixel permissions for.
3. In the right-hand column of the slide-out, select the **Details** tab.
4. In the *How we track* section, find *Pixel Piggyback* block.

   * If there is a green ![](/files/kaaz4vAVrKWGT3SfHUu1) **\[Check]** on the block, you can use piggyback pixels for this campaign.
   * If the block is greyed out, you cannot use piggyback pixels for this campaign.

   <div data-with-frame="true"><figure><img src="/files/jF4OHXe9OAxOtvkvWpDS" alt="" width="375"><figcaption></figcaption></figure></div>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.impact.com/partner/what-would-you-like-to-learn-about/platform-features/tracking/piggyback-pixels/find-piggyback-pixel-user-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.