Which connector?:

Spotify Ads

Additional details:

We’d like to sync Spotify’s attributed conversion metrics, especially attributed revenue, through the Spotify Ads custom aggregated report. Currently the Fields dropdown in the custom report setup does not offer them.

The Spotify Ads API v3.0 aggregate report endpoint (GET /ad_accounts/{ad_account_id}/aggregate_reports) accepts these fields, which are not available in v2.0:

• REVENUE
• PURCHASES
• AVERAGE_ORDER_VALUE
• RETURN_ON_AD_SPEND
• CUSTOMER_ACQUISITION_COST
• COST_PER_LEAD
• PAGE_VIEWS, LEADS, ADD_TO_CART, START_CHECKOUT, PRODUCTS, SIGN_UPS
• CUSTOM_EVENT_1 to CUSTOM_EVENT_5

Reference: https://developer.spotify.com/documentation/ads-api/reference/v3.0/getAggregateReport
Definitions: https://developer.spotify.com/documentation/ads-api/guides#metrics-glossary

Your release notes (July 2025) say the connector supports Spotify Ads API v3. However, the custom report field list appears to still be the v2.0 set, and the connector docs link to the v2.0 aggregate report reference.

Request:

1. Add the v3.0 conversion fields above to the custom report Fields selector, at minimum REVENUE and PURCHASES.
2. Allow these fields to be added to existing custom reports, with a historical re-sync so past data is backfilled.

Use case: we use platform-reported conversions and revenue alongside spend and delivery metrics for marketing measurement, and today Spotify is the only one of our ad platforms where we can’t get them through Fivetran.

Note: Spotify reports conversion counts between 1 and 4 as -5 for privacy. Please keep these values as returned (or document how they are handled), so they don’t break numeric column types.