Spotify has 494 million listeners on its ad-supported tier, and brands buying that audience want to see what it returns. Audio is brand marketing at heart. People hear the ad on the morning commute and act on it later, on whatever device is in front of them, without a click. Attribution still matters for that kind of campaign, and a click-based setup can't provide it.

MetaRouter now supports the Conversions API for Spotify Ads. Full-funnel conversion events, from website page views to mobile app purchases, flow to Spotify through your server-side pipeline. Each one carries the first-party identity signals Spotify uses to match a conversion back to the listener who heard the ad. The listener who hears your ad on their phone and buys on a laptop that evening now shows up in your Spotify results.

Server-side matching for Spotify conversions

Spotify matches conversions to listeners on first-party signals: the visitor's IP address, which is mandatory on every event, plus a hashed email, phone number, or mobile ad ID. MetaRouter captures those signals on your own domain at the moment of conversion, so Spotify receives the customer's real IP address and user agent, and email and phone are hashed with SHA-256 inside your private environment. A nightly warehouse job can't supply that real-time device context, and many server-side setups forward their own proxy IP in place of the customer's.

A single $0.00 test order can fail a whole batch of valid conversions on delivery to Spotify. Spotify rejects those orders, along with any event whose event_time falls outside its 30-day window. MetaRouter validates events in real time and filters both out before delivery, so valid conversions reach Spotify.

How it works

• Collect. Your first-party tag and mobile SDK send events from your own domain to your MetaRouter ingestion endpoint. No Spotify pixel on your site.
• Enrich and enforce. Every event carries your customer's IP, user agent, and hashed email, phone, or mobile ad ID. Your consent rules are enforced server-side before anything leaves your environment.
• Map. Pre-built mappings cover your full funnel: page and screen views, product views, add to cart, checkout started, and purchase. Web and app events are labeled automatically.
• Validate. Purchases are checked for currency and a non-zero amount, and timestamps for Spotify's 30-day window, so a bad event never costs you a batch of good ones.
• Deliver. Events are sent to Spotify's Conversions API from your infrastructure. You can see delivery in MetaRouter monitoring and results in the Spotify Ads Manager event activity graph.

The integration runs on the server-side pipeline you already use for your other destinations, so the conversions you send to Spotify are the same ones you send to Google, Meta, ChatGPT Ads, and your warehouse. Audio gets judged on the same data as every channel it competes with for budget.

Get started

To activate the integration, follow the Spotify CAPI setup documentation.

New to MetaRouter? Schedule a demo with our team to see how server-side integration recovers lost attribution across all your ad channels.

MetaRouter is the first-mile Customer Context Infrastructure that captures identity, behavior, and consent — in real time, inside the enterprise's own cloud, before the moment is lost. Trusted by global B2C enterprises including The Home Depot, Costco, Dicks Sporting Goods, and the world's largest Retail Media Networks. For more information visit: www.metarouter.io.