Skip to main content

Amazon Ads

This page contains the setup guide and reference information for the Amazon Ads source connector.

Prerequisites​

  • Client ID
  • Client Secret
  • Refresh Token
  • Region
  • Start Date (Optional)
  • Profile IDs (Optional)
  • Marketplace IDs (Optional)

Setup guide​

Step 1: Set up Amazon Ads​

Create an Amazon user with access to Amazon Ads account.

For Airbyte Open Source: To use the Amazon Ads API, you must first complete the onboarding process. The onboarding process has several steps and may take several days to complete. After completing all steps you will have to get Amazon client application Client ID, Client Secret and Refresh Token.

Step 2: Set up the Amazon Ads connector in Airbyte​

For Airbyte Cloud:

  1. Log into your Airbyte Cloud account.
  2. In the left navigation bar, click Sources. In the top-right corner, click + new source.
  3. On the source setup page, select Amazon Ads from the Source type dropdown and enter a name for this connector.
  4. Click Authenticate your Amazon Ads account.
  5. Log in and Authorize to the Amazon account.
  6. Select Region to pull data from North America (NA), Europe (EU), Far East (FE). See docs for more details.
  7. Start Date (Optional) is used for generating reports starting from the specified start date. Should be in YYYY-MM-DD format and not more than 60 days in the past. If not specified today's date is used. The date is treated in the timezone of the processed profile.
  8. Profile IDs (Optional) you want to fetch data for. See docs for more details.
  9. Marketplace IDs (Optional) you want to fetch data for. Note: If Profile IDs are also selected, profiles will be selected if they match the Profile ID OR the Marketplace ID.
  10. Click Set up source.

For Airbyte Open Source:

  1. Client ID of your Amazon Ads developer application. See onboarding process for more details.
  2. Client Secret of your Amazon Ads developer application. See onboarding process for more details.
  3. Refresh Token. See onboarding process for more details.
  4. Select Region to pull data from North America (NA), Europe (EU), Far East (FE). See docs for more details.
  5. Start Date (Optional) is used for generating reports starting from the specified start date. Should be in YYYY-MM-DD format and not more than 60 days in the past. If not specified today's date is used. The date is treated in the timezone of the processed profile.
  6. Profile IDs (Optional) you want to fetch data for. See docs for more details.
  7. Marketplace IDs (Optional) you want to fetch data for. Note: If Profile IDs are also selected, profiles will be selected if they match the Profile ID OR the Marketplace ID.

Supported sync modes​

The Amazon Ads source connector supports the following sync modes:

  • Full Refresh
  • Incremental

Supported Streams​

This source is capable of syncing the following streams:

Connector-specific features and highlights​

All the reports are generated relative to the target profile' timezone.

Campaign reports may sometimes have no data or not presenting in records. This can occur when there are no clicks or views associated with the campaigns on the requested day - details.

Report data synchronization only cover the last 60 days - details.

Performance considerations​

Information about expected report generation waiting time you may find here.

Data type mapping​

Integration TypeAirbyte Type
stringstring
int, float, numbernumber
datedate
datetimedatetime
arrayarray
objectobject

CHANGELOG​

VersionDatePull RequestSubject
3.4.12023-10-1331377Use our base image and remove Dockerfile
3.4.02023-06-0925913Add Stream DisplayCreatives
3.3.02023-09-2230679Fix unexpected column for SponsoredProductCampaigns and SponsoredBrandsKeywords
3.2.02023-09-1830517Add suggested streams; fix unexpected column issue
3.1.22023-08-1629233Add filter for Marketplace IDs
3.1.12023-08-2829900Add 404 handling for no assotiated with bid ad groups
3.1.02023-08-0800000Add T00030 tactic support for sponsored_display_report_stream
3.0.02023-07-2427868Fix attribution report stream schemas
2.3.12023-07-1128155Bugfix: validation error when record values are missing
2.3.02023-07-0628002Add sponsored_product_ad_group_suggested_keywords, sponsored_product_ad_group_bid_recommendations streams
2.2.02023-07-0527607Add stream for sponsored brands v3 purchased product reports
2.1.02023-06-1925412Add sponsored_product_campaign_negative_keywords, sponsored_display_budget_rules streams
2.0.02023-05-3125874Type portfolioId as integer
1.1.02023-04-2225412Add missing reporting metrics
1.0.62023-05-0925913Small schema fixes
1.0.52023-05-0825885Improve error handling for attribution_report(s) streams
1.0.42023-05-0425792Add availability strategy for basic streams (not including report streams)
1.0.32023-04-1325146Validate pk for reports when expected pk is not returned
1.0.22023-02-0322355Migrate products_report stream to API v3
1.0.12022-11-0118677Add optional config report_record_types
1.0.02023-01-3021677Fix bug with non-unique primary keys in report streams. Add asins_keywords and asins_targets
0.1.292023-01-2722038Set AvailabilityStrategy for streams explicitly to None
0.1.282023-01-1819491Add option to customize look back window value
0.1.272023-01-0521082Fix bug with handling: "Report date is too far in the past." - partial revert of #20662
0.1.262022-12-1920662Fix bug with handling: "Report date is too far in the past."
0.1.252022-11-0818985Remove "report_wait_timeout", "report_generation_max_retries" from config
0.1.242022-10-1917475Add filters for state on brand, product and display campaigns
0.1.232022-09-0616342Add attribution reports
0.1.222022-09-2817304Migrate to per-stream state.
0.1.212022-09-2717202Improved handling if known reporting errors
0.1.202022-09-0816453Increase report_wait_timeout 30 -> 60 minutes
0.1.192022-08-3116191Improved connector's input configuration validation
0.1.182022-08-2515951Skip API error "Tactic T00020 is not supported for report API in marketplace A1C3SOZRARQ6R3."
0.1.172022-08-2415921Skip API error "Report date is too far in the past."
0.1.162022-08-2315822Set default value for region if needed
0.1.152022-08-2015816Update STATE of incremental sync if no records
0.1.142022-08-1515637Generate slices by lazy evaluation
0.1.122022-08-0915469Define primary_key for all report streams
0.1.112022-07-2815031Improve report streams date-range generation
0.1.102022-07-2615042Update additionalProperties field to true from schemas
0.1.92022-05-0812541Improve documentation for Beta
0.1.82022-05-0412482Update input configuration copy
0.1.72022-04-2711730Update fields in source-connectors specifications
0.1.62022-04-2011659Add adId to products report
0.1.52022-04-0811430Add support OAuth2.0
0.1.42022-02-2110513Increasing REPORT_WAIT_TIMEOUT for supporting report generation which takes longer time
0.1.32021-12-288388Add retry if recoverable error occured for reporting stream processing
0.1.22021-10-016367Add option to pull data for different regions. Add option to choose profiles we want to pull data. Add lookback
0.1.12021-09-226367Add seller and vendor filters to profiles stream

Build instructions​

Build your own connector image​

This connector is built using our dynamic built process. The base image used to build it is defined within the metadata.yaml file under the connectorBuildOptions. The build logic is defined using Dagger here. It does not rely on a Dockerfile.

If you would like to patch our connector and build your own a simple approach would be:

  1. Create your own Dockerfile based on the latest version of the connector image.
FROM airbyte/source-amazon-ads:latest

COPY . ./airbyte/integration_code
RUN pip install ./airbyte/integration_code

# The entrypoint and default env vars are already set in the base image
# ENV AIRBYTE_ENTRYPOINT "python /airbyte/integration_code/main.py"
# ENTRYPOINT ["python", "/airbyte/integration_code/main.py"]

Please use this as an example. This is not optimized.

  1. Build your image:
docker build -t airbyte/source-amazon-ads:dev .
# Running the spec command against your patched connector
docker run airbyte/source-amazon-ads:dev spec

Customizing our build process​

When contributing on our connector you might need to customize the build process to add a system dependency or set an env var. You can customize our build process by adding a build_customization.py module to your connector. This module should contain a pre_connector_install and post_connector_install async function that will mutate the base image and the connector container respectively. It will be imported at runtime by our build process and the functions will be called if they exist.

Here is an example of a build_customization.py module:

from __future__ import annotations

from typing import TYPE_CHECKING

if TYPE_CHECKING:
    # Feel free to check the dagger documentation for more information on the Container object and its methods.
    # https://dagger-io.readthedocs.io/en/sdk-python-v0.6.4/
    from dagger import Container


async def pre_connector_install(base_image_container: Container) -> Container:
    return await base_image_container.with_env_variable("MY_PRE_BUILD_ENV_VAR", "my_pre_build_env_var_value")

async def post_connector_install(connector_container: Container) -> Container:
    return await connector_container.with_env_variable("MY_POST_BUILD_ENV_VAR", "my_post_build_env_var_value")

| 0.1.0 | 2021-08-13 | 5023 | Initial version |

Was this page helpful?