> 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 →** [**Brands**](https://app.impact.com/secure/mediapartner/marketplace/new-campaign-marketplace-flow.ihtml).
2. Select the brand for which you want to test your piggyback pixel.
3. From the brand's slide-out, select ![](https://347878556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2Fgit-blob-8ec3e877b1397045c61d394485e72ac4d93120ee%2Fc6ddb46c637059f06e86c790a911217a9428f5c47b5efef046f90555e85b03cd.svg?alt=media) **\[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 ![](https://347878556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2Fgit-blob-df93ac0f80fc5cece7983980a5ce3fbcf19aabce%2F3ef9d737089bc07dbb7e4fd41a97edfbaec261e4f55ab3a1666f3daf957f69c3.svg?alt=media) **\[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 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/what-would-you-like-to-learn-about/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.