> 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/test-piggyback-pixels.md).

# Test Piggyback Pixels

Testing a piggyback pixel ensures that your third-party tracking systems are correctly receiving conversion data from impact.com. This article walks you through how to locate and test a piggyback pixel for a specific brand, verify that it's firing correctly, and confirm that conversions are being tracked end-to-end. Whether you're a brand, creator, or direct partner, following these steps helps validate your pixel setup and maintain accurate performance tracking.

1. From the top navigation bar, select **Discover → My Brands**.
2. Select the brand for which you want to test your piggyback pixel.
3. From the brand's slide-out, select ![](/files/QmaL30TflEtQDgN6tzCe) **\[More]** → **Tracking Integration**.
4. In the *Media Partner Tracking Pixels* table, find the piggyback pixel you want to test, then under the *Actions* column, select ![](/files/Q8zbLIZ7lLJJAhDIZzDX) **\[Drop-down menu]** → **Test**.
5. In the new window, enter the landing page URL and select **Launch Test**.
6. You will get redirected to a page with two options.
   * If the internal tracking test URL has been properly set up, you will be led to the landing page for the tested campaign. Select **Trigger Conversion Piggyback**, and impact.com will call the pixel, which will show up as a conversion in your third-party tracking system.
   * Continue through the brand's conversion path and complete an end-to-end test. This will show up as a transaction in your third-party system and as a pending action in 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 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/test-piggyback-pixels.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.