Support Amazon-Ads-AccountId header as alternative to Amazon-Advertising-API-Scope for DSP Reporting
Answered
Details: Which connector?: Amazon Ads reporting connector.
Additional details: This request arises from the discussion in https://support.fivetran.com/hc/en-us/requests/381383. We'd like the connector to support the Amazon-Ads-AccountId header instead of Amazon-Advertising-API-Scope. The endpoint remains the same (/reporting/reports) — this is purely a header swap. The current implementation requires profile-level admin access to populate profileIds via GET /v2/profiles, which forces customers to grant elevated permissions they don't want to give. The AccountId header allows limited access to a single advertiser without administrator-level provisioning. This is currently blocking 3 advertisers (Jobber, Dave, Sonos) across 3 agency partners.
-
Official comment
Hi Steven,
Thanks for the request. From our understanding you are requesting this to be supported on the Amazon DSP connector? Cos the Amazon Ads connector do not have this capability. Can you please reconfirm?
Thanks. -
Hi Unnikrishnan,
Thanks for looking into this. To be honest, I don't know the exact name of the connector on your side — that was confirmed by Monica Patel (Support Engineer) in ticket https://support.fivetran.com/hc/en-us/requests/381383 as part of the investigation. What I can tell you is that the connector in question is whichever one uses the /reporting/reports endpoint documented here: https://advertising.amazon.com/API/docs/en-us/offline-report-prod-3p#tag/Asynchronous-Reports/operation/createAsyncReport.
The ask remains the same: support the Amazon-Ads-AccountId header as an alternative to Amazon-Advertising-API-Scope on that endpoint, so customers don't need to grant profile-level admin access via GET /v2/profiles.
Can you coordinate with Monica's ticket to confirm which connector this maps to on your end?
Thanks,
Steven
Please sign in to leave a comment.
Comments
2 comments