Integrations / Advertising
Spotify Ads Manager
Server-side conversion delivery to the Spotify Conversions API (CAPI) for tagless attribution. Maps Signal events to Spotify's standard event enum (Page_View, View_Product, Add_Cart, Start_Checkout, Purchase, Lead, Sign_Up), hashes email/phone with SHA-256, forwards IP + user agent for identity matching, and honours marketing consent via opt_out_targeting.
Datafly Signal delivers first-party events to Spotify Ads Manager server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Spotify Ads Manager expects.
Why route Spotify Ads Manager through Datafly Signal
Conversions survive ad blockers and tracking prevention
A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Spotify Ads Manager optimises against are not filtered by the browser.
Email and phone number hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Spotify Ads Manager receives match keys rather than raw personal data.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what Spotify Ads Manager needs to attribute the event to the right session.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Spotify Ads Manager rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Spotify Ads Manager is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_to_cartbegin_checkoutgenerate_leadpagepurchasesign_upview_itemVertical presets
Retail. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Spotify Ads Manager documentation.
Frequently asked questions
Does Datafly Signal integrate with Spotify Ads Manager?
Yes. Datafly Signal delivers first-party events to Spotify Ads Manager server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Spotify Ads Manager expects. The integration is included in every deployment at no additional cost.
How is server-side Spotify Ads Manager tracking different from the Spotify Ads Manager tag?
The Spotify Ads Manager tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Spotify Ads Manager from your server, so delivery does not depend on browser conditions.
What personal data is sent to Spotify Ads Manager?
Email and phone number are normalised and SHA-256 hashed inside your own deployment before delivery, so Spotify Ads Manager receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Spotify Ads Manager?
The blueprint ships with mappings for add_to_cart, begin_checkout, generate_lead, page, purchase, sign_up, view_item. Any event in your schema can be mapped to Spotify Ads Manager through pipeline configuration without a code change.
Do I need to keep the Spotify Ads Manager tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so Spotify Ads Manager deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Spotify Ads Manager server-side?
See how Datafly Signal delivers first-party events to Spotify Ads Manager from infrastructure you control, with hashed identity and consent enforcement built in.