Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Support delivery_goal_group (campaign) and delivery_goal (ad set) fields in the Spotify Ads connector

Answered
Ryan McCaffrey User

Spotify has recently deprecated their objectives field, which we were previously ingesting in the campaigns table of our Fivetran Spotify Ads connector. After communication with the Spotify team, they recommended that the new way to ingest this data is by fetching the delivery_goal_group field at the Campaign level and the delivery_goal field at the Ad Set level.

The Fivetran Spotify Ads connector calls Ads API v3 (shipped July 2025), but the two new attributes Spotify recommends, delivery_goal_group (Campaign) and delivery_goal (Ad Set), are not yet included in the schema. They therefore don’t appear in the standard CAMPAIGN/AD_SET tables or in the Custom Report field picker.

This is a feature request for the addition of both the delivery_goal_group and delivery_goal fields to their respective tables for the Spotify Ads connector. Without these fields, we are unable to deduce the objectives for any new data from Spotify since June 26, 2025, which is when Spotify began to deprecate the old "objectives" column out of their API.

Please sign in to leave a comment.

Comments

5 comments

Date Votes
  • Official comment
    Lucas Alexander Fivetranner

    Hi Ryan, 

    Thanks for flagging this!

    I checked Spotify's documentation for the endpoints we use to retrieve campaign and ad_set data. "delivery_goal_group" isn't listed as an available field from the /campaigns endpoint. "delivery_goal" isn't available from the /ad_sets/ endpoint either. However, "objective" is listed as an available field for both endpoints. They don't list "deliver_goal_group" or "delivery_goal" in their reporting endpoint documentation either. 

    Did the Spotify team explain how they expect advertisers to retrieve this data?

    Thanks,
    Luke 

  • Ryan McCaffrey User

    Hey Luke,

    Thanks for the reply -- I agree, I do not see these fields documented in the Spotify API documentation either and I have reached back out to Spotify's technical team to understand this a bit more. It might be helpful if you also connect with Spotify's technical team on your end. For visibility, here's the exact email I got from Spotify's team when I asked about the objective field deprecation:

    After reviewing the API changes, we confirmed that the null values that the advertiser is seeing in the objective field are expected behavior. This is not a bug, but a result of Spotify transitioning their API architecture.

    The Technical Detail: Spotify Ads API is replacing the legacy objective field with a new structure. To get the data we need, the ingestion logic must change:

    • Previously: We only needed to fetch the objective field at the Campaign level.

    • Now (Required): We must fetch delivery_goal_group at the Campaign level, and crucially, we must now also fetch delivery_goal from the Ad Set level to get the correct objective data.

  • Lucas Alexander Fivetranner

    Thanks for sharing that, Ryan.

    We will reach out to Spotify, too. I asked because sometimes Fivetran customers receive faster responses than we do from source companies. Fivetran's customers are spending money with these source platforms. Sometimes their support teams ignore Fivetran's outreach because we aren't paying customers of theirs. But I'll try regardless!

  • Lucas Alexander Fivetranner

    Hi Ryan,

    Our support team let me know Spotify updated its public docs. I've added this to our team's backlog to start working on it.

    I'll post an update here when it's picked up.

    Cheers,
    Luke

  • Peter Chang User

    Hi @Lucas Alexander

    Is there a way to increase this work on the backlog priority?
    And possible timeline as to when this work might get picked up?