Measure outcomes with Spotify Pixel and Conversions API
Understand what happens after someone is exposed to your ad by measuring selected outcomes—from sign-ups to sales. Pixel and Conversions API connect ad exposure to actions across your website, app, and offline channels, so you can see what’s driving results.
Campaigns that used these solutions together saw a 29% higher conversion rate and 12% lower cost per action than those using one of the two tools.¹
How Spotify Pixel and Conversions API work together
Spotify Pixel and Conversions API can each be used independently, but together they provide a more complete view of campaign performance. Browser-side and server-side signals are deduplicated to improve measurement coverage while helping reduce signal loss.
| Spotify Pixel Measure website actions with browser-based measurement. | Conversions API Measure website, app, and offline actions with server-side integration. | Together (suggested) Get a more complete view of performance with deduplicated measurement across eligible sources. |
Measure website actions with Spotify Pixel
Pixel is a browser-based measurement tag that helps you understand what people do on your website, from sign-ups to purchases, after being exposed to a Spotify ad. Pixel helps you:
Measure website actions across devices
Connect ad exposure across mobile, desktop, and connected devices to actions people take on your website.
Build audiences based on site activity
Use your event data to create custom web event audiences for retargeting, or build lookalike segments based on site behavior to reach people more likely to convert.
Understand what’s driving performance
Measure conversions and see how performance varies across audiences, formats, genres, streaming contexts, and other delivery dimensions to understand what’s associated with stronger business outcomes.
How to get started with Spotify Pixel
Pixel captures select website events and connects them to Spotify ad exposure using first-party attribution. Here’s how to set it up:
Install the JavaScript code on your website directly or via Google Tag Manager.
Check the Event Activity graph in Ads Manager to confirm your Pixel is sending conversion event data.
Choose your Pixel as the conversion data source during campaign setup to begin measuring results.
For detailed setup instructions, see the Pixel help center article.
| Pixel capabilities and requirements | |
| Setup requirement | Must install Spotify Pixel on advertiser website |
| Measurable formats | All Ads Manager formats |
| Conversion sources | Website |
| Reporting metrics | Page views, leads, adds-to-cart, purchases, revenue, average order value (AOV), return on ad spend (ROAS), customer acquisition cost (CAC), cost per lead, start checkouts, product views, sign-ups, custom events |
| Flight length | Suggested 4-week minimum |
Track actions across web, app, and offline with Conversions API
Conversions API is a server-based attribution solution that sends conversion data to Spotify, enabling measurement across web, app, and offline events. It provides a comprehensive view of how your campaigns drive results across devices and environments. Conversions API helps:
Use one integration to better understand conversions across your website, app, and offline channels in a single view.
Use conversion data in Ads Manager to create audiences based on real user behavior.
Capture events through server-side integration to reduce signal loss from browser limitations.

How to get started with Spotify Conversions API
Conversions API sends conversion data directly from your server to Spotify. Here’s how to set it up:
For detailed setup instructions, see the Conversions API help center article.
| Ads Manager capabilities | |
| Integration methods | Server-to-server or Google Tag Manager (server-side) |
| Measurable formats | All Ads Manager formats |
| Conversion sources | Website, app, and/or offline |
| Reporting metrics | Page views, leads, adds to cart, purchases, revenue, average order value, return on ad spend, customer acquisition cost, cost per lead, start checkouts, product views, sign ups, custom event |
| Flight length | Recommended 4-week minimum |
| Direct IO capabilities and requirements | |
| Integration methods | Server-to-server or Google Tag Manager |
| Setup requirements | Must have an Ads Manager account |
| Measurable formats | All Direct IO formats |
| Conversion sources | Website, app, and/or offline |
| Reporting metrics | Page views, leads, adds to cart, purchases, revenue, average order value, customer acquisition cost, cost per lead, start checkouts, product views, sign ups, custom event |
| Flight length | Recommended 4-week minimum |
Frequently asked questions
Spotify Pixel supports all formats available in Ads Manager.
Conversions API supports all formats that are available with Ads Manager and Direct IO.
Yes, measurement capabilities differ between buying channels. While there are many consistencies across them, there are a few differences.
For both Ads Manager and Direct IO campaigns, Pixel and Conversions API support measurement across all formats available within each buying platform, along with standard conversion metrics (e.g., page views, leads, purchases, revenue). Ads Manager also includes capabilities such as custom audience creation, real-time reporting, and optimization toward supported campaign objectives.
Ads Manager can show how conversion performance varies across supported delivery dimensions such as audience, genre, streaming context, device, and format. These insights can help inform future targeting, format, budgeting, and campaign planning decisions.
Start measuring outcomes with Pixel and Conversions API
Sources & References