Spotify Ads connector

Set up the Spotify Ads connector in Kaivo: authentication, configuration, the 3 BigQuery tables it syncs, and answers to common questions.

Written By Lauri Raivio

Last updated About 3 hours ago

Kaivo is a fully managed data platform that syncs your Spotify Ads data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your marketing and sales data instead of moving it.

What is the Spotify Ads connector

Sync your Spotify Ads data into BigQuery with Kaivo to track ad spend and performance alongside your other channels.

CategoryMarketing & Sales
StatusGenerally available
AuthenticationAPI key
SetupSelf-service

Getting started with the Spotify Ads connector

  1. Sign up for Kaivo and create a workspace.
  2. Connect your Spotify Ads account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Authenticating Spotify Ads

Authenticate with your Spotify Ads credentials. You provide:

FieldDescription
Client Secret

The Client Secret of your Spotify developer application.

Refresh Token

The refresh token obtained from the OAuth 2.0 authorization flow.

Prerequisites

Spotify Ads only supports OAuth, so you need your own Spotify developer application with Ads API access. You must have a Spotify Ads Manager account to use this connector.

  1. Register a developer application in the Spotify for Developers dashboard, selecting Ads API when asked which APIs you plan to use. Note its Client ID and Client Secret, and add a redirect URI (e.g. http://127.0.0.1:8080/callback).
  2. Accept the Ads API Terms for your Client ID — requests fail until this is done.
  3. Complete the OAuth 2.0 authorization-code flow once to obtain a Refresh Token (see Spotify's authorization guide).

Then enter those values below along with your Ad Account ID.

Note: Spotify expires refresh tokens 6 months after authorization, so you'll need to repeat step 3 and update the Refresh Token roughly twice a year.

Need help? Reach our team via the chat in the bottom-right corner.

Configuring the Spotify Ads connector

When you set up the connector, you provide:

FieldDescription
Client ID

The Client ID of your Spotify developer application.

Ad Account ID

The ID of the Spotify Ad Account to sync data from.

Start Date

Any data before this date will not be fetched.

Report Fields

List of fields to include in the campaign performance report.

Tables and columns synced from Spotify Ads

Kaivo syncs 3 tables from Spotify Ads into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

How the Spotify Ads sync works

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Spotify Ads supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won't get duplicate rows.

Frequently asked questions

How long does the initial sync take for Spotify Ads?

It depends on how much history is in your Spotify Ads account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they're much faster.

Can I sync only some tables or columns?

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don't select are never copied to your warehouse.

What happens when Spotify Ads's schema changes?

New fields are never added automatically. You choose which fields to sync, so data you haven't selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table's sync mode: full-refresh tables always match what's currently in Spotify Ads, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

How do I handle GDPR or data deletion requests?

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Spotify Ads instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Spotify Ads connector in Kaivo and all of its synced data is deleted with it.

Common use cases for Spotify Ads data

Cross-channel reporting

Use campaign_performance to compare Spotify cost and results with your other ad platforms.

Campaign performance

Join campaigns with campaign_performance to track impressions and conversions over time.

Account view

Use ad_accounts to report on spend across your accounts.

Use Spotify Ads data in your AI and BI tools

Once Spotify Ads data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here's how the most common destinations work with Spotify Ads data.

Claude

Use Kaivo's MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Power BI

Microsoft's BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Data Studio

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

Tableau

The premium analytics standard, with native BigQuery integration. Setup guide →

Google Sheets

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Excel

Connect via Power Query's BigQuery connector. Setup guide →

Metabase

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for Spotify Ads connector pricing and plan details.