Manage Piggyback Pixels as a Partner

Normally, when a conversion happens, the news moves from your brand's website to impact.com's internal system, and then from there to you. This 2-step transfer can cause a minor delay before the conversions you drive appear in your reporting. Piggyback pixels act as a shortcut to intercept this data directly from the brand's website. Learn more.

Manage your piggyback pixels

1. From the top navigation bar, select Discover → My Brands.
2. Select the brand you want to manage the piggyback pixel for, then select More → Tracking Integration.
3. For the event type (formerly action tracker) you want to manage the piggyback pixel for, under the Actions column, select [Drop-down menu] → Edit.
4. Read the notice and select I understand, continue.
5. Select the tracking pixel type.
6. Add the tracking pixel code or image source URL.
7. If you want to add more parameters to your piggyback pixel, select Show/hide optional parameters. Refer to the Optional URL parameters for more information.
8. Select Save.

   1. When a confirmation page with the piggyback pixel loads, the pixel fires the data it has tracked over to the tracking software with a browser cookie linking you to the order confirmation.
   2. Remember that piggyback pixels only need a browser cookie to fire, so you may experience false positives and false negatives. This can lead to unmet template terms, last clicks not registering, and other incorrect reports.

Note: False positive actions may be invalidated if not corrected before the action locking cycle ends. Other invalidation events include registering with a duplicate order ID, exceeding template terms for action recurrences, and lacking an active template term between the brand and partner, often due to misfiring piggyback pixels.

Optional URL & item-level parameter reference

URLs can include optional parameter values. These parameters are dynamically replaced with actual values when the URL loads.

URL parameters all build around the same URL template, which is https://www.domain.com?[Parameter]={Example}. When the URL is called, {Example} will fill with the data that the [Parameter] value requests.

URL parameters reference

URL Parameter	Description
{CampaignId}	The ID of your partnered brand.
{ActionTrackerId}	The ID of the action tracker you're adding a piggyback pixel to.
{MediaPartnerId}	The ID of the partner (which is you).
{SaleAmount}	The sale amount of the action, which is expressed in the brand's preferred currency. This can only be tracked for sale actions.
{Currency}	The original currency of the action, AKA the currency used to buy the product or service.
{Network_SaleAmount}	The amount of money the action product, which is expressed in the brand's preferred currency. This can only be tracked for sale actions.
{PromoCode}	The promo code for the action.

• Item-level parameters can also be added to your piggyback pixel. These tell you more about what exactly was sold, how much was sold, and more.
• Like URL parameters, item-level parameters also build around one template. In this case, the format is {join(items,i,"[Function]{i}={i.[Function]}","&","?")}. Whatever item-level parameter you want tracked needs to replace [Function].
• For example, if you wanted to track the sku number of sold products, your parameter would be {join(items,i,"sku{i}={i.sku}","&","?")} and would result in ?sku1=[sku 1 number]&sku2=[sku 2 number]... continuing for the amount of items sold in that action.