Skip to main content
This page compares the Spotify Ads capabilities represented in the Interchange adapter with what Interchange currently makes available to buyers. It answers a practical question: what can I do through Interchange today, and what would still require another path?
Last reviewed 2026-08-18. This is Interchange’s description of its own adapter, based on the implementation and the linked provider documentation. Spotify Ads has not reviewed or endorsed this page. Availability can still vary by account permissions, market, and provider access.

​
At a glance

​
How to read availability

  • 🟢 Available — Offered through Interchange now, subject to your ad account’s permissions and eligibility with the provider.
  • 🟡 Partial — Some of the workflow is available; the Comments column explains the boundary.
  • 🔵 Testing — Interchange is validating the workflow before offering it broadly.
  • ⚪ Planned — Not offered through Interchange yet. The provider may still support it directly; Comments explains why and links a roadmap reference.

​
Roadmap

The adapter roadmap is tracked in AI-1944 (a plain-text reference — Interchange’s internal issue tracker is not public). This roadmap tracks Spotify product completeness, provider limits, and live readiness. Every row that is not currently available shows that reference or a more specific one in its References column, so customers and partners can quote a stable identifier when asking about a capability.

​
Connection, accounts, and identity

Spotify Ads connects to Interchange through an OAuth grant. Connecting a Business account gives Interchange access to each Ad account it can reach — you then map each one to your advertisers. The mapped account decides which Spotify Ads tenant a buy runs on: a media buy for an unmapped advertiser fails closed with account_mapping_required rather than silently using another account. Connection, account-discovery, and revocation behavior is the same across ad platforms — see Platform accounts and advertiser mapping for the full model and the Spotify Ads section of the connecting guide for Spotify Ads-specific permissions.

​
Campaign products

​
Creative formats

These rows describe Interchange availability, not a claim that the ad platform itself prohibits an unavailable format.

​
What the adapter can do

​
Placement choices

Interchange does not expose a separate Spotify Ads placement selector.

​
Targeting

​
Reporting

Interchange reports Spotify Ads delivery day by day (there is no hourly delivery breakdown), aggregated nightly from adapter-reported delivery, in the advertiser’s home currency using the booked or historical exchange rate — any cross-currency rollup is always labeled an estimate and is never used for billing. See Reporting overview for the full model. Interchange does not currently publish an attribution-finality window for Spotify Ads; the table below lists every metric the adapter surfaces today.

​
Webhooks and async lifecycle

Spotify Ads does not push status, delivery, or reporting events into Interchange — every campaign product declares supports_webhooks: false.
  • Status. Interchange does not currently poll Spotify Ads in the background for creative or media-buy status changes; status reflects what the adapter returned on your last call.
  • Delivery. Interchange has not yet made on-demand delivery fetching generally available for Spotify Ads — see Get Media Buy Delivery in “What the adapter can do” above. The /reporting/metrics endpoints never call the adapter either way — they read from a separately-populated store (see Reporting below), so a reporting request does not itself refresh provider delivery.
This is separate from Interchange’s own buyer webhook subscriptions — an unrelated account-level event feed (currently discovery.revision only), documented in Buyer webhooks.

​
Market and account availability

Interchange does not promise that every feature is enabled for every account or market. Availability is checked against your selected ad account rather than a global market list on this page.

​
Important limitations

  • Interchange implementation/testing. This page is not yet a confirmed complete catalog of every Spotify Ads creation path.
  • Interchange implementation/testing. The listed campaign products exist in the current adapter code but are still being certified before general availability.
  • the ad platform’s API or your account’s eligibility. Brief planning interprets objective, age, geography, interests, format, and podcast context. A recommendation does not guarantee that the selected Spotify account can execute it.
  • the ad platform’s API. The Spotify Ads API does not expose terminal campaign cancellation through this integration. Pause is reversible, and Interchange never reports it as canceled.
  • Interchange implementation/testing. Existing Spotify custom audiences can be listed and deleted. Lookalike audiences are read-only, and no audience can be created, changed, included, or excluded from campaign targeting through Interchange.
  • both Interchange’s implementation and the ad platform’s API or account eligibility. Product selection fixes Spotify-owned in-stream or in-feed delivery; there is no separate placement selector. Placement reporting is returned only after provider readback confirms music-only inventory and no off-Spotify impressions.
  • Interchange implementation/testing. Spotify audio formats are listed for planning, but Interchange does not yet offer audio audition or a complete creative preview, submission, and readback workflow.

​
Technical mapping

Engineering-level detail — raw provider objectives, billing enums, optimization codes, and object-field mappings. Not required reading to understand what Interchange can do with Spotify Ads; see the tables above for that.

​
Provider documentation