Advertising
AI agent for Spotify Ads: campaign reports, ad-set budgets, bids and paused-first builds
TL;DR
Spotify Ads connects through Spotify's own sign-in to the Spotify Ads API and reads every ad account your Spotify login reaches in Spotify Ads Manager. The agent reports on music, podcast and video campaigns, changes budgets, bids and targeting you approve, and builds campaigns and ad sets that start without spending. The Ads API has no delete for campaigns, ad sets or ads — pause is the stop — and anything that turns spending on waits for a person every time.
Connecting it
- 1Open Integrations and click Connect on the Spotify Ads card.
- 2Sign in to Spotify with the account that has a role on your ad account in Spotify Ads Manager, and allow access.
- 3Pick the ad account for the task, then write the goal.
Access requirements
- A Spotify Ads Manager account. The Spotify login you connect with must belong to a business with at least one ad account in Spotify Ads Manager (adsmanager.spotify.com). Otherwise the connect succeeds and the account list stays empty with that reason until you press Refresh accounts.
- The Ads API Terms. Spotify opens its Ads API only to an app whose client id has accepted the Spotify Ads API Terms (adsmanager.spotify.com/api-terms). Until that is done every call is refused; once accepted, Spotify's allowlist can take up to an hour. This is a one-time step for whoever runs the deployment — if connecting says the Ads API refused access, ask your administrator, then press Refresh accounts (you do not need to connect again).
- No permissions to pick. The Ads API needs no OAuth scopes: the consent screen asks only to let the app act for your account, and the agent reaches exactly the ad accounts your role allows.
- The connection renews itself. Spotify's refresh tokens do not expire on a clock, but you can revoke the app's access in your Spotify account at any time; the card then asks you to sign in again.
What the agent reads
- Every business and ad account your Spotify login reaches, with its status, your role and its currency.
- Campaigns, ad sets (budget, bid, schedule, targeting, delivery) and ads (call to action, tracking, review status), and creative assets — audio, image and video.
- Performance by campaign, ad set, ad or the whole account — impressions, clicks, spend, reach, frequency, completions, listeners and more — per day, per hour or for the lifetime, in UTC days and up to 90 days at a time; larger exports run as a CSV.
- Audience and bid estimates for an ad set shape, the targeting catalogues (genres, artists, playlists, podcast topics, interests, languages, places) and the account's change history.
What the agent changes — all of it approval-gated
- Create campaigns and ad sets. A campaign carries no budget; an ad set is created with delivery off, whatever the API's default.
- Budgets, bids, schedules and targeting on ad sets — the ad set is read first and the approval shows it before and after.
- Ads — the call to action, its clickthrough URL (with your UTM parameters) and third-party tracking, edited in place.
- Creative assets — upload audio, image or video files for your ads, including your own background music.
- Pause campaigns, ad sets and ads.
Turning spending on always waits for a person: activating a campaign, switching an ad set or an ad on, publishing a draft campaign, writing an audience and editing the ad account's own record are never auto-approved, never part of a batch, never on a schedule and never from an autonomous API key. There is no delete for campaigns, ad sets or ads on the Ads API, and archiving was removed by Spotify — pause is the stop.
The Web Playback SDK is not part of this
- Agent Planners does not use Spotify's Web Playback SDK. It is a browser player for Spotify Premium listeners (it asks for the streaming, user-read-email and user-read-private permissions), it needs Spotify's written approval for commercial use, and it cannot play your own ad audio.
- Spotify's Developer Policy forbids pairing its music with advertising. Ad audio and background music for your ads go through the Ads API's own audio assets — files you upload — never music from Spotify's catalogue.
Things worth knowing before you plan around it
- One Spotify login can reach several ad accounts, so every call names the selected account; an id that belongs to another account is refused before anything is sent.
- Amounts are shown in each ad account's own currency, in whole units — Spotify's micro units are converted at the boundary.
- Reports use UTC days, and small conversion counts Spotify masks for privacy come back empty rather than as zero.
- Budgets and bids meet an absolute ceiling, and a change far outside the current value waits for a person even under auto-approve.
Frequently asked questions
- Does Agent Planners support Spotify Ads?
- Yes. Eighteen reads and ten approval-gated writes on the Spotify Ads API cover ad accounts, campaigns, ad sets, ads, creative assets, reports, estimates and targeting, plus budget, bid, targeting, tracking and paused-first creates; turning spending on waits for a person every time.
- Why does connecting say the Ads API refused access?
- Spotify opens its Ads API only to an app that has accepted the Spotify Ads API Terms. Your administrator accepts them once for the deployment; it can take up to an hour to take effect, and then Refresh accounts lists your ad accounts — no second sign-in needed.
- Can the agent spend money on its own?
- No. New ad sets start with delivery off, and activating a campaign or switching an ad set or ad on always needs a person's approval — also under auto-approve or from an API key.
- Can it delete campaigns?
- No — the Spotify Ads API has no delete for campaigns, ad sets or ads, so the agent pauses instead.
- Can it use music from Spotify in my ads?
- No. Spotify's Developer Policy forbids pairing its music with advertising. Upload your own ad audio or background music as an audio asset instead.