1. Who should install the Spotify Pixel? 

The Spotify Pixel must be installed by the brand or website owner. You will need access to the source code of your website to install the pixel unless you’re using a 3rd party partner integration, such as Google Tag Manager.

 

2. What types of ads can be measured?

The Spotify Pixel can measure campaigns booked via Ads Manager, including audio and video ads on Spotify, including audio, video, and display ads on Spotify. 

 

3. When does the Spotify Pixel need to be installed to measure my campaign?

It is best practice to install your pixel at least one to two weeks before the start of a campaign to give yourself time to make sure Spotify is receiving conversion events from your website. If your pixel is not installed on your website, or is installed incorrectly, your campaign's performance data will be inaccurate. Data cannot be collected retroactively.

 

4. Will the Spotify Pixel slow down my website?

Our JavaScript loads asynchronously, which means it will not significantly increase load times of your website or the pages the JavaScript code is on.

 

5. Why does Spotify require a JavaScript pixel instead of an image pixel?

JavaScript pixel implementation is required to get the most comprehensive information and realistic story of attributed events. Ads Manager does not support image pixels for conversion measurement. 

 

6. What is a Lead event? 

Lead events are website events where people might provide their personal contact information for the first time and that info could be used to generate future sales. (ex. sign up for a newsletter, schedule an appointment, request a quote, etc). An advertiser might use this type of conversion event to measure the effectiveness of a campaign intended to generate sales leads.

 

7. Why should the main pixel script be installed on multiple pages of the website?

Placement on at least 3 pages provides Spotify with 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. The better the pixel coverage of your website, the higher the opportunity to map a user’s action on your website back to an ad impression.

 

8. Do you support Content Security Policy (CSP)?

If you are using a Content Security Policy, you will need to add the following two lines:

script-src 'unsafe-inline' https://pixel.byspotify.com;
connect-src https://pixels.spotify.com;

 

9. Where permitted by the advertiser, does the Spotify Pixel place a cookie? 

When an advertiser installs the Spotify Pixel on their website, the pixel fires each time a user visits the site, meaning the JavaScript code runs and sends data about the visit to Spotify.

 

When you enable first-party cookies within your pixel settings, the pixel will store a first-party cookie in the user’s browser. This cookie is used to help recognize the browser and associate subsequent actions on the site with the same user session, helping provide more complete and accurate measurement and attribution.

 

When you disable first-party cookies, the pixel will still send event data to Spotify, but it will not store or access a first-party cookie for that browser.

 

Cookie information:

  • Cookie Name: __spdt (or pdst for legacy ones)

  • Duration: 12 months

  • Type: first-party

  • Function: stores Pixel ID