Skip to main content

Amazon Ads

Amazon Ads is an online advertising platform that helps businesses of all sizes promote their products and brands across Amazon's properties and beyond, offering sponsored ads, display advertising, and performance analytics to drive sales and customer engagement.

Amazon Ads icon

Power end-to-end data operations for your Amazon Ads API with Nexla. Our bi-directional Amazon Ads connector is purpose-built for Amazon Ads, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Amazon Ads or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Amazon Ads workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating an Amazon Ads credential in Nexla, you need to set up an OAuth 2.0 integration in the Amazon Advertising API and obtain the required credentials. Amazon Ads API access is available through different URL endpoints depending on your region.

OAuth 2.0 Setup

  1. Access Amazon Advertising API: Sign in to your Amazon Advertising account and navigate to the Amazon Advertising API documentation.

  2. Register Your Application: Register your application with Amazon to obtain OAuth 2.0 credentials. This process generates the OAuth 2.0 client credentials that you'll use for authentication.

  3. Configure OAuth Settings: Configure your OAuth application settings, including redirect URIs and scopes. The redirect URI should match the callback URL provided by Nexla during the OAuth flow.

  4. Select API Endpoint: Determine which Amazon Ads API endpoint you need based on your region:

    • North America (NA): https://advertising-api.amazon.com
    • Europe (EU): https://advertising-api-eu.amazon.com
    • Far East (FE): https://advertising-api-fe.amazon.com
  5. Select Authorization URL: Choose the appropriate authorization URL for your region:

    • North America: https://www.amazon.com/ap/oa
    • Europe: https://eu.account.amazon.com/ap/oa
    • Far East: https://apac.account.amazon.com/ap/oa
  6. Select Token URL: Choose the appropriate token URL for your region:

    • North America: https://api.amazon.com/auth/o2/token
    • Europe: https://api.amazon.co.uk/auth/o2/token
    • Far East: https://api.amazon.co.jp/auth/o2/token
  7. Obtain Client Credentials: Copy your OAuth 2.0 client credentials from your OAuth application settings. These credentials are used to authenticate with the Amazon Advertising API.

  8. Select OAuth Scope: Choose the appropriate OAuth scope based on the APIs you want to access:

    • advertising::campaign_management: For DSP, Sponsored Brands, Sponsored Display, Sponsored Products, and Amazon Attribution APIs
    • advertising::audiences: For Data Provider API
    • advertising::test:create_account: Only for Test APIs
    • advertising::test:create_account advertising::campaign_management advertising::audiences: For complete API access, including creation of test accounts

    The OAuth scope determines which APIs your application can access. Choose the scope that matches your use case. For detailed information about Amazon Ads API authentication and OAuth setup, see the Amazon Advertising API documentation.

Authenticate

Credentials required

FieldRequiredSecretDescription
Amazon Ads API EndpointYesNoAmazon Ads API access is available through different URL endpoints. Choose the one applicable for you. Allowed values: North America (NA): https://advertising-api.amazon.com; Europe (EU): https://advertising-api-eu.amazon.com; Far East (FE): https://advertising-api-fe.amazon.com
Authorization URLNoNoLogin with Amazon implements a different authorization URL prefix for each region. Select the URL for your region. Allowed values: North America: https://www.amazon.com/ap/oa; Europe: https://eu.account.amazon.com/ap/oa; Far East: https://apac.account.amazon.com/ap/oa
ScopeNoNoThe OAuth 2.0 permission scope used to limit the application's access to an advertiser's account. Allowed values: advertising::campaign_management (Set this scope for the DSP, Sponsored Brands, Sponsored Display, Sponsored Products, and Amazon Attribution APIs.); advertising::audiences (Set this scope for the Data Provider API.); advertising::test:create_account (Only for Test APIs. These APIs allow Amazon Ads customers to test and learn about API functionality.); advertising::test:create_account advertising::campaign_management advertising::audiences (Set this scope for complete API access, including creation of test accounts.)
Token URLNoNoAmazon Ads Token URL Allowed values: North America: https://api.amazon.com/auth/o2/token; Europe: https://api.amazon.co.uk/auth/o2/token; Far East: https://api.amazon.co.jp/auth/o2/token

Create a credential in Nexla

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Amazon Ads

AmazonAdsCred.png
  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  2. Select the Amazon Ads API endpoint that matches your region from the Amazon Ads API Endpoint dropdown menu. Available options include:

    • North America (NA): https://advertising-api.amazon.com
    • Europe (EU): https://advertising-api-eu.amazon.com
    • Far East (FE): https://advertising-api-fe.amazon.com
  3. Select the authorization URL that matches your region from the Authorization URL dropdown menu. Available options include:

    • North America: https://www.amazon.com/ap/oa
    • Europe: https://eu.account.amazon.com/ap/oa
    • Far East: https://apac.account.amazon.com/ap/oa
  4. Select the OAuth scope from the Scope dropdown menu based on the APIs you want to access. Available options include:

    • advertising::campaign_management: For DSP, Sponsored Brands, Sponsored Display, Sponsored Products, and Amazon Attribution APIs
    • advertising::audiences: For Data Provider API
    • advertising::test:create_account: Only for Test APIs
    • advertising::test:create_account advertising::campaign_management advertising::audiences: For complete API access
  5. Select the token URL that matches your region from the Token URL dropdown menu. Available options include:

    • North America: https://api.amazon.com/auth/o2/token
    • Europe: https://api.amazon.co.uk/auth/o2/token
    • Far East: https://api.amazon.co.jp/auth/o2/token
  6. Complete the OAuth authorization flow by following the prompts to authorize Nexla to access your Amazon Ads account. The OAuth flow will automatically handle token exchange and refresh.

    The OAuth 2.0 flow provides secure, token-based access to the Amazon Advertising API with automatic token refresh. Ensure that you select the correct region-specific endpoints and URLs to match your Amazon Advertising account location. For detailed information about Amazon Ads API authentication, see the Amazon Advertising API documentation.

  7. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Amazon Ads connector tile, then select the credential that will be used to connect to the Amazon Ads instance, and click Next; or, create a new Amazon Ads credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Amazon Ads endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get all Profiles

This endpoint retrieves all profiles associated with your Amazon Advertising account. Profiles represent an advertiser and their account's marketplace, and are used in all subsequent API calls via a management scope.

  • This endpoint automatically retrieves all profiles from your Amazon Advertising account. No additional configuration is required beyond selecting this endpoint template.
  • The endpoint will return profile information including profile IDs, advertiser names, marketplace information, and other profile metadata.

Profile IDs obtained from this endpoint are required for many other Amazon Ads API operations. For detailed information about retrieving profiles, see the Amazon Advertising API documentation.

Get Audiences

This endpoint returns a list of audience segments for an advertiser. Use this endpoint when you need to access audience data for targeting, analysis, or integration with other systems.

  • Enter the Profile ID of the advertiser whose audiences you want to retrieve in the Profile ID field. Profile IDs can be obtained by first using the "Get all Profiles" endpoint.
  • The endpoint uses token-based pagination, automatically fetching additional pages as needed. The endpoint retrieves audiences using the nextToken parameter to handle pagination efficiently.
  • The endpoint will return all audience segments for the specified advertiser, including audience names, IDs, and metadata.

This endpoint supports pagination through nextToken parameters. Nexla automatically handles pagination to retrieve all available audiences. For detailed information about retrieving audiences, see the Amazon Advertising API documentation.

Get Audience Insights: Overlap Audiences

This endpoint retrieves the top audiences that overlap with a provided audience. Use this endpoint when you need to discover similar or overlapping audience segments for targeting and analysis.

  • Enter the Profile ID of the advertiser in the Profile ID field. Profile IDs can be obtained by first using the "Get all Profiles" endpoint.
  • Enter the Audience ID of the audience you want to analyze in the Audience ID field. Audience IDs can be obtained by first using the "Get Audiences" endpoint.
  • Select the ad type from the Ad Type dropdown menu. This determines which type of advertising data is used for the overlap analysis.
  • The endpoint uses token-based pagination, automatically fetching additional pages as needed. The endpoint will return overlapping audience information including overlap percentages and audience details.

This endpoint supports pagination through nextToken parameters. Nexla automatically handles pagination to retrieve all available overlapping audiences. For detailed information about audience insights, see the Amazon Advertising API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Amazon Ads data sources can also be manually configured to ingest data from any valid Amazon Ads API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Amazon Ads API endpoints typically follow the pattern {api_url}/v2/{endpoint} or {api_url}/{endpoint}, where {api_url} is your region-specific API endpoint. Some Amazon Ads API endpoints require the Amazon-Advertising-API-Scope header with a Profile ID value.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Amazon Ads data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Amazon Ads destination, and select the Send to Destination option from the menu. Select the Amazon Ads connector from the list of available destination connectors, then select the credential that will be used to connect to the Amazon Ads organization, and click Next; or, create a new Amazon Ads credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Amazon Ads endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Upload Hashed Records

This endpoint saves Nexset records of hashed personally-identifiable information (PII) to be matched with Amazon identities for future use. Use this endpoint when you need to upload customer data for audience targeting and matching. All inputs must be properly normalized and SHA-256 hashed as defined in the API documentation.

  • The endpoint will send the Nexset data as JSON in the request body to upload hashed records. Ensure your Nexset contains properly normalized and SHA-256 hashed PII data according to Amazon's requirements.
  • The endpoint uses batch processing, automatically grouping records into batches of up to 2000 records per API call for efficient data upload.
  • Each batch of records will be sent as a separate API request to upload hashed records to your Amazon Advertising account.

The request body must contain valid JSON with properly normalized and SHA-256 hashed PII data. All data must be hashed according to Amazon's specifications before uploading. For detailed information about data requirements and hashing specifications, see the Amazon Advertising API documentation.

Manual configuration

Amazon Ads destinations can also be manually configured to send data to any valid Amazon Ads API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Amazon Ads API endpoints typically expect JSON format for request bodies and follow the pattern {api_url}/{endpoint}, where {api_url} is your region-specific API endpoint. For update/upsert operations, include the ID of the object to be updated at the end of the URL. Some Amazon Ads API endpoints require specific headers like Amazon-Advertising-API-Scope with a Profile ID value.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Amazon Ads endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Amazon Ads endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.