Skip to main content

Amazon Ads Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to an Amazon Ads location.
amzads_api.png

Amazon Ads

Create an Amazon Ads Destination​

  1. 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.

  2. 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.

  3. In Nexla, Amazon Ads destinations can be created using pre-built endpoint templates, which expedite destination setup for common Amazon Ads endpoints. Each template is designed specifically for the corresponding Amazon Ads endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Amazon Ads destinations can also be configured manually, allowing you to send data to Amazon Ads endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Amazon Ads endpoints. Each template is designed specifically for the corresponding Amazon Ads endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, 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.

Configure Manually​

Amazon Ads destinations can be manually configured to send data to any valid Amazon Ads API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Amazon Ads API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Amazon Ads API from the Method pulldown menu.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Amazon Ads API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. Amazon Ads API endpoints typically expect JSON format for request bodies.

API Endpoint URL​

  1. Enter the URL of the Amazon Ads API endpoint to which you want to send the Nexset data in the URL field. For update/upsert operations, include the ID of the object to be updated at the end of the URL. Amazon Ads API endpoints typically follow the pattern {api_url}/{endpoint}, where {api_url} is your region-specific API endpoint.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Some Amazon Ads API endpoints require specific headers like Amazon-Advertising-API-Scope with a Profile ID value.

    You do not need to include any headers already present in the credentials.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Amazon Ads destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100. For Amazon Ads endpoints that support batching, you may need to adjust this value based on API requirements.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings. Some algorithms require additional settings—click on an algorithm listed below to view instructions for configuring these settings.

Response Webhook​

Optional

Nexla can automatically send the response received from the Amazon Ads API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Amazon Ads API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Amazon Ads API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Amazon Ads API using the current settings.

Save & Activate the Destination​

  • 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.