Skip to main content
This page compares the Spotify Ads capabilities represented in the Apostra adapter with what Apostra currently makes available to buyers. It answers a practical question: what can I do through Apostra today, and what would still require another path?
Last reviewed 2026-11-18. This is Apostra’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 Apostra 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 — Apostra is validating the workflow before offering it broadly.
  • ⚪ Planned — Not offered through Apostra 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 — Apostra’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 Apostra through an OAuth grant. Connecting a Business account gives Apostra 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

Optional maximum CPM bidding

Every Spotify product uses Spotify’s own automated bidding (AUTOBID) when a package omits bid_price. To set a cap, supply a positive packages[].bid_price. Apostra uses Spotify’s MAX_BID strategy and treats the value as the maximum cost per 1,000 impressions (CPM), as indicated by max_bid: true on the product’s pricing option. Create a package with bid_price set from the start to use maximum-CPM bidding: a package created with no bid cannot gain one later through update_media_buy, which refuses the update rather than silently applying it, and a maximum-CPM package cannot be moved back to automated bidding through update_media_buy either, since clearing bid_price is refused rather than silently dropped. Updating the bid amount on an existing maximum-CPM package is supported. Reads reflect the bid Spotify actually applied: a package booked without a bid reads back with no bid_price, never a stale or invented value. The maximum-bid mapping has automated contract and unit-test coverage, but it has not yet been validated against a live Spotify account; account permissions and eligibility remain authoritative.

Pricing notes

pricing_options omits floor_price and price_guidance for every Spotify product. Spotify exposes no discovery-time bid estimate, so a static per-template guess was never a real floor, and unlike other adapters it was applied unconditionally regardless of account currency. Each product is still priced (pricing_model, currency); there is simply no platform-backed number to bid against yet.

Creative formats

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

Create a creative

A complete, runnable save_creative call for Audio Standard, one of the formats listed above: formatKind: "audio_hosted", paired with a formatOptionRef naming the product’s own format option. Replace campaignId, name, and the asset URLs with your own.
Audio Standard also requires a companion image at least 640x640px and no larger than 200 KB, and these three authored text slots: headline (25 characters or fewer), brand_name (25 characters or fewer), and call_to_action (one of LEARN_MORE, SHOP_NOW, SIGN_UP, DOWNLOAD, LISTEN_NOW, WATCH_NOW, or BOOK_NOW). This save_creative call validates and saves today. Spotify Reach’s own audio workflow (audition, submission, and faithful readback) is still in testing, as the Creative formats table above shows — check there for current delivery readiness. Send the same call with validateOnly: true to check assets and text against the format before saving anything — no Creative, no draft row:

What the adapter can do

Placement choices

Apostra does not expose a separate Spotify Ads placement selector.

Targeting

Audiences and segments

Existing Spotify audiences are found with get(kind: “audience”) and attached to a campaign with targetingOverlay audience_include or audience_exclude by Spotify id. Not available through Apostra for Spotify Ads: Interests and purchase intent, Advanced demographics beyond age, Genres, Tone, Activities, Fan bases. A campaign brief does not apply any of this: Spotify is wholesale-only, and it never reads a brief.

Reporting

Apostra does not yet offer Spotify Ads delivery reporting through this adapter. Once available, Apostra reports 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. The table below lists every metric the adapter is built to surface.

Webhooks and async lifecycle

Spotify Ads does not push status, delivery, or reporting events into Apostra — every campaign product declares supports_webhooks: false.
  • Status. Apostra 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. Apostra 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 Apostra’s own buyer webhook subscriptions — an unrelated account-level event feed (currently discovery.revision only), documented in Buyer webhooks.

Market and account availability

Apostra 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

  • Apostra implementation/testing. This page is not yet a confirmed complete catalog of every Spotify Ads creation path.
  • Apostra implementation/testing. The listed campaign products exist in the current adapter code but are still being certified before general availability.
  • Apostra implementation/testing. get_products does not accept a brief for this adapter. A request that includes one is refused with UNSUPPORTED_FEATURE; retry with buying_mode “wholesale” and no brief to receive the full catalogue.
  • Apostra implementation/testing. A campaign brief is not read by a wholesale-only seller like Spotify at all, not just refused at get_products: there is no brief-derived targeting or product selection anywhere in the flow for these sellers. Set targeting explicitly in targetingOverlay instead.
  • the ad platform’s API. The Spotify Ads API does not expose terminal campaign cancellation through this integration. Pause is reversible, and Apostra never reports it as canceled.
  • the ad platform’s API. The Spotify Ads API has no targeting control for Connected devices, In-Car, or Web, even though Spotify’s Ads Manager offers them as Device options and Spotify’s own reporting can measure delivery by device bucket. Device targeting through Apostra is limited to iOS, Android, and Desktop.
  • the ad platform’s API. Spotify’s own forecaster refuses to create an ad set whose targeting is too narrow to reach a minimum of 100 projected unique users (commonly hit with a small postal code set in geo_postal_areas); the campaign it would have belonged to is left paused, the same as any other Spotify Ad Set creation failure. Apostra reports the rejection as AUDIENCE_NOT_DELIVERABLE, naming the projected count and the minimum, so broadening your targeting (for example, adding more or wider postcodes) is the fix.
  • Apostra implementation/testing. Existing Spotify custom audiences can be listed and deleted. Lookalike audiences are read-only, and no audience can be created or have its members changed through Apostra. A campaign can include or exclude an existing audience by naming its Spotify id.
  • both Apostra’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.
  • Apostra implementation/testing. Spotify audio formats are listed for planning, but Apostra does not yet offer audio audition or a complete creative preview, submission, and readback workflow.
  • Apostra implementation/testing. Spotify Ads Manager’s own UI also offers Genres, Tone, Activities and settings, Fan bases, and demographic options beyond age as targeting choices. None of these is available through Apostra today, so there is nothing for a buyer agent to send and nothing for Apostra to accept or refuse for them. Segment-style demographics and interest categories may become available as signals once Apostra adds Spotify segment targeting (AI-20589).

Technical mapping

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

Provider documentation