# Amazon Ads

## Amazon Advertising Console (Amazon Ads)

This guide explains how a client can authorize Connecty to sync **Amazon Ads** data (Sponsored Products/Brands/Display + reports) into Connecty’s managed warehouse.

### Overview

Connecty syncs Amazon Ads via the **Amazon Ads API** (Sponsored Products, Sponsored Brands, Sponsored Display + reporting). ([Airbyte Docs](https://docs.airbyte.com/integrations/sources/amazon-ads))

### Prerequisites (Client)

Client must provide:

* **Client ID**
* **Client Secret**
* **Refresh Token**
* **Region** (NA / EU / FE)
* (Optional) **Start Date**
* (Optional) **Profile IDs**
* (Optional) **Marketplace IDs** ([Airbyte Docs](https://docs.airbyte.com/integrations/sources/amazon-ads))

> **Important account-type limitation:** the connector supports **seller/vendor** type profiles; **agency** profiles are ignored / not compatible for Sponsored Ads APIs. ([Airbyte Docs](https://docs.airbyte.com/integrations/sources/amazon-ads))

### Step 1 — Create an Amazon user with Ads access

Client should ensure they have an Amazon user who can log into the **Amazon Advertising Console** and has access to the relevant advertiser accounts. ([Airbyte Docs](https://docs.airbyte.com/integrations/sources/amazon-ads))

### Step 2 — Authorize / Provide credentials (two common paths)

#### Path A (preferred): OAuth “Authenticate your Amazon Ads account”

If Connecty is running an OAuth-style flow (like Airbyte Cloud):

1. Client clicks **Authenticate your Amazon Ads account**
2. Logs in and **Authorizes**
3. Selects **Region** (NA/EU/FE)
4. (Optional) sets Start Date / Profile IDs / Marketplace IDs ([Airbyte Docs](https://docs.airbyte.com/integrations/sources/amazon-ads))

#### Path B: Client provides credentials to Connecty

If Connecty is running a credentials-based setup:

* Client shares **Client ID, Client Secret, Refresh Token**, and **Region** with Connecty Support (secure channel). ([Airbyte Docs](https://docs.airbyte.com/integrations/sources/amazon-ads))

### Configuration details (what these fields mean)

* **Region:** North America (NA), Europe (EU), Far East (FE). ([Airbyte Docs](https://docs.airbyte.com/integrations/sources/amazon-ads))
* **Start Date (optional):** `YYYY-MM-DD`, must be **≤ 60 days in the past** for report generation; defaults to **today** (Cloud) or **yesterday** (some OSS behavior). ([Airbyte Docs](https://docs.airbyte.com/integrations/sources/amazon-ads))
* **Profile IDs (optional):** choose which advertising profiles to sync (seller/vendor only). ([Airbyte Docs](https://docs.airbyte.com/integrations/sources/amazon-ads))
* **Marketplace IDs (optional):** filter profiles by marketplace; if Profile IDs are also set, selection matches **Profile ID OR Marketplace ID**. ([Airbyte Docs](https://docs.airbyte.com/integrations/sources/amazon-ads))

**Profiles concept note:** Amazon Ads “profiles” represent an advertiser + marketplace, and are used as scope for subsequent API calls. ([Amazon Ads](https://advertising.amazon.com/API/docs/en-us/reference/2/profiles?utm_source=chatgpt.com))

### Supported sync modes and streams

* **Sync modes:** Full Refresh, Incremental ([Airbyte Docs](https://docs.airbyte.com/integrations/sources/amazon-ads))
* **Common streams (examples):** Profiles, Portfolios, Sponsored Products/Brands/Display entities and multiple report types. ([Airbyte Docs](https://docs.airbyte.com/integrations/sources/amazon-ads))

### Validation Checklist (Connecty)

Connecty Support confirms:

* ✅ Credentials/OAuth authorization works
* ✅ Profiles discovered and correct ones selected
* ✅ Streams populate (campaigns, ad groups, keywords, ads, targetings, reports)
* ✅ First sync completes


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://connectyai.gitbook.io/documentation/getting-started/data-connections-guide/amazon-ads.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.