Amazon ads
Prerequisites
- Client ID
- Client Secret
- Refresh Token
- Region
- Start Date (Optional)
- Profile IDs (Optional)
Setting up the Amazon ads connector
| No | Item | Required | Example | Notes |
|---|---|---|---|---|
| 1 | Auth Type | No | ||
| 2 | Client ID | Yes | The client ID of your Amazon Ads developer application. See the docs for more information. | |
| 3 | Client Secret | Yes | The client secret of your Amazon Ads developer application. See the docs for more information. | |
| 4 | Refresh Token | Yes | Amazon Ads refresh token. See the docs for more information on how to obtain this token. | |
| 5 | Region | No | Region to pull data from (EU/NA/FE). See docs for more details. | |
| 6 | Start Date | No | 2022-10-10 2022-10-22 | The Start date for collecting reports, should not be more than 60 days in the past. In YYYY-MM-DD format |
| 7 | Profile IDs | No | Profile IDs you want to fetch data for. See docs for more details. | |
| 8 | State Filter | No | Reflects the state of the Display, Product, and Brand Campaign streams as enabled, paused, or archived. If you do not populate this field, it will be ignored completely. | |
| 9 | Look Back Window | No | 3 10 | The amount of days to go back in time to get the updated data from Amazon Ads |
| 10 | Report Record Types | No | Optional configuration which accepts an array of string of record types. Leave blank for default behaviour to pull all report types. Use this config option only if you want to pull specific report type(s). See docs for more details |
Zipstack Cloud features a powerful SQL querying engine on top of many types of connectors, including those from Trino, some custom connectors and connectors from the open source Airbyte project. Some Zipstack cloud connectors are designed to utilize and expand upon Airbyte's connector protocol, but they do not use Airbyte's EL core. Additionally, some parts of the documentation for these connectors have been adapted from the connector documentation found in Airbyte's open source project.