1. Ad Analytics Help Center
  2. Getting Started
  3. 3. Install the Spotify Pixel or RSS Prefix

Install the Spotify Pixel

A step-by-step guide on the one-time installation of the Spotify Pixel.

Applies to: Brands

First time using Spotify Ad Analytics?
Follow these instructions to configure your brand in order to generate and install the Spotify Pixel. Learn more about the Spotify Pixel here

Create a Pixel

  1. Start by selecting all installation methods you will be using by clicking the Methods drop-down menu. JavaScript is the default, but we offer integrations with trusted partners.  Learn more about each here.

    Install the Spotify Pixel_1
  2. Next, input your website domain in the Website URL field.
    • Optional: Toggle on Alias Events if you wish to match conversions back to your internal systems.  This allows advanced users to 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.
  3. You must select who will handle the pixel installation. That can either be you or another member of your organization.  
  4. Finalize the process by clicking Create Pixel

Main Pixel Script

The Main Pixel Script collects Page Views and visits, and is required to start tracking activity on your website. You will need to install the Main Pixel Script snippet on at least 3 pages of your website, however, we recommend that you place it on every page. The more website data we receive, the more attribution data we can provide!

    • Why does the main pixel script need to be installed on multiple pages of the website?
      • Placement on at least 3 pages provides us the baseline information needed to ensure the pixel is firing and capturing traffic. Any less will not provide enough data to accurately run attribution on a given campaign.

Add Events

Next, you will be prompted to Add Events.  From here, you can choose just to Add 1 Required Event (Page View), or create additional events.  Your Page View pixel will collect page views for web and mobile installs for mobile. Depending on which type of installation method you choose in the previous step, that is what will show by default.  To add another event:

  1. Choose descriptive & accurate event names so your colleagues know what's what!  The event names you create will show up in the dashboard and in reporting exactly as you have entered them here.

    1. Note: Don't worry if you missed a few things here -- you'll have the opportunity to edit and add to this list later.
  2. Type your event into the Event Name field to search the most commonly used events. If you do not find an event you need, you can also create a Custom event.  

Install the Spotify Pixel_2

Generate Additional Event Pixels

This part is easy!  You can add new pixel events at any time and our tools will generate the code for you based on your inputs -- no need to edit the code. 

  1. Navigate to Manage > Your Pixels and click onto the alpha-numeric Pixel ID.
  2. From here, you will see the pixel(s) you have already setup and you will see the option to Add New Event.  
    • Note: To edit any events you have already setup, click the pencil icon.
  3. After editing or adding, the pixel code will automatically be generated for you to use based on your installation method.  Directly copy and paste this code and Save Event.
Install the Spotify Pixel_3-1

Install and verify the Pixel(s)

You're almost there! Each individual pixel needs to be installed on your website or app. The Spotify Pixel can be installed directly on your site, or through third-party integrations. Note: While we support third-party installation, we are unable to troubleshoot third-party installations.

Verify the pixel is collecting the data you need. Our tools will show you if data is being collected, but we cannot verify if it's collecting the right information. Verify that your Spotify pixel installation is accurate by confirming the following:
  1. Event log graph shows activity at the expected volume.  Hover over the graph to compare its activity to your internal data.  Example: if your website typically receives 10,000 visits per day, but your graph shows 5,000 per day, then the pixel may not have been installed site-wide.  In this case, you should re-verify pixel installation. 
  2. Verified event table shows activity as expected.  Use the Installation column to confirm if the pixel is installed.  If it is installed, use the Last Activity column to determine when the pixel last fired.  To ensure each pixel is passing back relevant data, click the pencil icon to view details.
    1. Note: The verification tools show all website activity – not just attributed activity.

Screenshot 2023-06-12 at 10.58.22 AM