Podsights Pixel for Websites or Apps

Learn about what the Podsights pixel is, how it may be used, and how to install it.

Applies to: Brands, Agencies


Podsights is a reporting and attribution platform for podcast advertising. To effectively measure the performance of a campaign, Podsights integrates with the podcast via an Analytics Prefix (appended within the RSS feed of the podcast) or your hosting provider's Tracking URL and the brand's site via our JavaScript SDK. 

What does that actually mean? To activate Podsights attribution measurement, an advertiser pixels their website (or app) to fit the other half of the attribution puzzle piece. 

There are two pixel categories you should understand:

  1.  Visits - when a user downloads a podcast with your ad, then visits your website, a visit is registered. The sum of your visitors makes up your overall conversion rate, so your goal should be to capture anywhere a podcast listener may visit on your site. Place the main pixel on your website's homepage, landing page(s), and across the website, especially places where one may be directed from search or social. The main pixel will collect page views and unique household visits within the attribution window. 
  2. Conversions - depending on your campaign KPIs, you may want to install additional pixels to understand not just how many households are visiting, but what actions they are taking. Common conversion events include: 
    1. Podsights pre-categorizes conversion event types for you as either a lead, purchase, etc.  

How to install a Podsights pixel

A Podsights pixel should be installed at least two weeks before the beginning of a campaign. While it's not a technical requirement, the timeline allows for enough runway to troubleshoot or alter the pixel as needed. If your pixel is not installed or is installed incorrectly, your campaign's performance data will be inaccurate or incomplete. There's no way to retroactively receive your website data, which is why installation is so critical. 

First time using Podsights? 

  1. Configure Brand: When you log in for the first time, you will have to associate your organization with a brand.
    1. Type in your brand name in the Brand Name field to see if it exists already. If it already exists, the Brand Industry may automatically populate.
    2. If it populates the wrong industry or does not populate at all, you can use the drop down menu to select the correct industry for your brand.
    3. Once you're ready, you can click Create brand to start 
      Screen Shot 2022-04-29 at 2.43.50 PM
    1. create your brand, you will be automatically prompted to generate a pixel per your KPIs.
  2. Create a Pixel: Next, you will be automatically prompted to generate a pixel per your KPIs.
    1. Start by selecting all the methods of installation you will be using by using the drop-down menu. By default, it will be JavaScript but we have integrations with Apps Flyer, Branch, Adjust and Kochava. You learn more about each here.
      Screen Shot 2022-04-29 at 5.06.02 PM
    2. Next, you will need to input your brand website domain in the Pixel Domain field. This will be your pixel's label.
    3. Optional: Toggle on Alias Events if you wish to match conversions back to your internal systems.
      • For advanced users, you can optionally pass us an internal user ID along with each event, which we can pass back to you when reporting on conversions. You can then match back the conversions we attribute with your internal systems.
    4. In order to create a pixel, you must also select the point of contact for actually installing the pixel by using the drop-down menu. That can either be you or another member of your organization. Screen Shot 2022-04-29 at 5.06.12 PM
  3. Add Events: Your pixel will collect page views for web and mobile installs for mobile. Depending on which type of installation you chose in the previous step, that is what will show by default. While you must have at least one event, you may also add as many more events as you see fit. To add another event: 
    1. Type into the Event Name field and search for some of the most commonly used events. 
    2. If you do not find an event you need, you can also create a Custom event. 
    3. Be sure to make your labels descriptive so your colleges know what's what! Keep in mind the event names will show up in the dashboard and in reporting. 
    4. You will always be able to edit and add more events after so don't worry if you missed a few things or want to skip this step for now.
      CleanShot 2022-05-04 at 14.04.20

  4. Now to generating event pixels: This part is easy! Our tools will generate the code for you based on your inputs. No need to edit the code snippet. 
    1. Start by going to Manage Your Pixels and click on the line item with the Domain you are looking to install.
    2. Once selected, it should open the page for you to edit the pixel. Here is where you can edit and add more events.
    3. After editing or adding, the dashboard should automatically generate a code for you to use based on your installation method.
  1. You're almost there! Time to actually install the code: Each individual pixel needs to be installed on your website or app. The Podsights pixel can be installed directly on your site, via GTM and other third parties.
    1. While we support third-party installation, we cannot troubleshoot any third-party installations.
    2. Need help? If you or your developer need help, let us know. Our Platform Success Engineers can assist the folks installing the pixel. Keep in mind that we will be able to speak to our code, not necessarily how to explicitly install it on your website.  
  2. Verify the pixel is collecting the data you need. Our tools will show you if data is being collected or not, but we cannot verify if it's collecting the right information. *Keep in mind that the verification tools show all activity on your website, not just attributed activity*  Verify your pixel installation by seeing if the:
    1. Event log graph shows activity at the expected volume.  Compare the daily activity to your internal data.  Example: if your website typically receives 20,000 visits per day, but your graph shows 10,000 per day, then the pixel was likely not installed across the full site. If the graph shows 100 events per day, it's likely that the pixel was installed only on the homepage or on one landing page. In this case, you would resend the pixel URL to your developer with instructions to install and check activity.
    2. Verified event table shows activity as expected. Now we need to ensure that the data we need is being sent. For example, if we are tracking a purchase event on a check out page, we want to ensure that we are not only registering the event, but also that we are being passed relevant data like product name or value of purchase. 

Best Practices

Place your unique Podsights main pixel script to collect views and visits. You will need to install the Main Pixel Script snippet in at least 3 pages, however, we recommend that you place the main pixel on every page of your website. The more website data, the more attribution data!


Need to access or generate a new pixel?

Login to dash.podsights.com and ensure your Brand is configured. Then, navigate to Manage > Pixels and choose or create your pixel. 

Please view additional website, mobile, and RSS prefix documentation here