Skip to main content

Introduction

Spotify Ads (Spotify Advertising) is Spotify’s self-serve platform for audio, video, and podcast campaigns delivered to listeners across the Spotify app and web player. The connector ingests ad account, campaign, ad set, and ad performance from the Spotify Ad Analytics API, including audio-specific signals such as streams, listeners, and skips alongside standard reach and click metrics. As a marketing connector, metrics, breakdowns, and currencies are standardized so widgets can aggregate across sources without additional configuration. To connect this data source, see How to connect Spotify Ads to Adriel.

Data refresh strategy

Architecture data

Architecture covers ad accounts, campaigns, ad sets, and ads. It refreshes twice daily, at 4:00 PM UTC and 5:00 AM UTC.

Reports data

Reports include daily performance for ad accounts, campaigns, ad sets, and ads. Real-time. Report data is fetched from Spotify on demand when a dashboard loads, so the latest values are always visible. On top of that, scheduled cache refreshes keep historical data consistent across multiple time windows. Refresh schedule. Reports refresh on three overlapping schedules:
  • 5:00 PM UTC daily — syncs the last 9 days for ad account, campaign, ad set, and ad
  • 11:40 PM and 6:40 AM UTC daily — syncs the last 3 days for ad account, campaign, ad set, and ad
  • 7:30 AM UTC on the 1st and 15th of each month — syncs the last 30 days for ad account, campaign, ad set, and ad

Architecture levels

Ad account → Campaign → Ad set → Ad

Date range limits

The Spotify API rejects report ranges longer than 90 days, so wide date ranges are split into 90-day windows automatically. In addition, the connector enforces these maximum look-back windows per breakdown:

Metrics

How to read the columnsData type uses Adriel’s vocabulary — Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean. API Key in code style like IMPRESSIONS is the literal Spotify Ad Analytics API field; italic marks a value Adriel computes or derives on its side rather than a single API field. Some raw fields back several metrics — for example STARTS backs both Video Impressions and Views, and LISTENERS / REACH back the listener-rate metric — so the same key can appear on multiple rows; that’s the shared source field, not a duplicated entry. Currency values are reported in each ad account’s configured Spotify Ads currency.

Campaign Attributes

Campaign Structure

Click Performance

Currency conversion. Each ad account’s currency comes from its Spotify Ads settings. When an ad account’s currency differs from the workspace currency, costs are automatically converted using the current day’s exchange rate.

Computed Metrics

These are calculated by Adriel from other metrics; they have no single underlying Spotify Ads field.

Conversion Performance

Creative Attributes

Engagement

Video Performance

Spotify Ads-specific

These metrics exist only for Spotify Ads and aren’t part of any cross-connector category. Every group above is a standard category shared with other connectors.

Breakdowns

Campaign Structure

Channel, Platform, and Status groupings are provided by Adriel for cross-connector consistency rather than returned by Spotify.

Creatives

Adriel post-processes ad creatives to generate these breakdowns.

Date

Spotify’s API returns daily records only; Adriel groups them into these views for reporting, so all time-grouping breakdowns are Adriel-side aggregations of the same underlying daily data.

Others

Limitations

  • No demographic, geographic, or placement breakdowns — the connector exposes only level and date breakdowns. Fields such as country, region, DMA, platform, and hour exist in the Spotify API but are not surfaced in Adriel.
  • Daily data only from the source — Spotify returns daily granularity; weekly and monthly views are aggregated client-side by summing the underlying daily rows.
  • 90-day request window — the Spotify API rejects report ranges longer than 90 days. Wide ranges are fetched in 90-day chunks, which can make very wide date ranges slower to load.

API references

See also