Connector name:
Amazon Ads

Table name:
New tables requested (none exist today):

• ads_account: global advertising accounts, from POST /adsAccounts/list
• ads_account_alternate_id: one row per alternate ID (entityId, profileId, countryCode) linking each global account to the existing profile table
• Existing tables affected: profile, campaign_history (and other tables that carry profile_id)

API documentation link:
Amazon Ads API: https://advertising.amazon.com/API/docs (Accounts API, POST /adsAccounts/list)

I couldn't verify the exact deep link to the Accounts API page, so please paste that in before submitting.

Additional details:
The connector currently identifies accounts only through the legacy profiles model. The profile table exposes the numeric profile id and an account_id containing the legacy ENTITY ID (e.g. ENTITY5M6RWD93NRSW). Amazon's unified global ads account ID (e.g. amzn1.ads-account.g.6sp7pc5beqhf100hvs7kmzuiu) isn't available anywhere in the synced schema.

We need:

1. The global ads account IDs synced. Populate ads_account from POST /adsAccounts/list, including adsAccountId, account name, status and country codes.
2. A link between global IDs and entity IDs. The API returns alternateIds (entityId, profileId, countryCode) per account. Syncing these lets us join the global ID to profile.account_id (ENTITY ID) and profile.id (profile ID).
3. A link between campaigns and the global ID. campaign_history currently carries only profile_id. Please either add an ads_account_id column or document a supported join path through the mapping table. Ideally this also covers ad group, ad and report tables.

Desired outcome: a documented join path of global ads account ID → entity ID → profile ID → campaign, without custom code outside Fivetran.

Current workaround: we call the Accounts API ourselves and join on entityId or profileId. That adds a pipeline to maintain and risks drifting out of sync with the connector.

Business impact: [add your use case here, e.g. the downstream systems that key on the global ID].

Related request (different scope): Amazon-Ads-AccountId header support covers authentication scope for reporting, not exposing the account ID in the synced data.