1. Pixel
  2. Website Pixel

Using Podsights Debugger

The Debugger is a tool used to confirm that your website pixel is firing. In addition, it allows you to view your website specific data.

Applies to: Brands and Agencies

The Debugger will help you answer questions like:

  • Are all of my website pixel events firing? 
  •  Which webpages are my pixel events happening on?
  • How can I see exactly what is being sent through the pixel? 

To view your debugger, navigate to Manage > Your Pixels.   From there,  click on your alpha-numeric pixel ID and select Debugger.  

NOTE: You can filter the debugger to show specific events (ex: purchases, leads, etc..), and you can also filter it to show mobile-only events if you have mobile events setup with Podsights. 

The Debugger and Event Mappings for Mobile Integrations 


NOTE: This section only applies if you are using a Mobile Integration and need to map events to Podsights' standard conversion events.

If you are utilizing one of our supported Mobile Integrations and are tracking mobile events for your campaign, you may need to map your mobile event action if the name of the action event being sent to Podsights, does not match any of the Podsights standard actions as listed below:

  • Lead
  • Purchase
  • Add To Cart
  • Product
  • Install
  • Checkout

To add event mappings for your mobile events, navigate to Manage > Your Pixels. From there,  click on your alpha-numeric pixel ID and select Event Mappings.  

NOTE: The Event Mappings Feature only applies to mobile events and does not work for JS or Image events


Click on the Add Mapping button, located in the top right corner of the page. Enter in the exact event name pulled from your mobile partner and then select the standard conversion event or Podsights action that should be mapped to your event name. The formating is sensitive for this feature so please be sure to check the formatting in Podsights matches your formatting for the event in your mobile integration partner.


When you're done, click on Save Event Mapping to save the mapping.


Once you've saved your mappings, they will begin to populate into the debugger after attribution has run, because the raw pixel data will need to be parsed, curated and mapped with the settings that you have just saved.


NOTE: The Debugger will only show up to 100 of your most recent events at a time, so this will apply to the event mappings that fit this criteria.