# Amazon Ads DSP and AMC Destination ## Destination Info * Accepts [Track](/docs/segment/connections/spec/track) calls. * Refer to it as **Amazon AMC (Actions)**, **Amazon Ads DSP and AMC** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object) * This destination is **Beta.** [Amazon Ads](https://advertising.amazon.com/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) can help you achieve your marketing goals, whether that's building brand awareness, driving sales, or increasing customer loyalty. The Segment - Amazon Ads DSP and AMC integration allows users to connect their Engage Audiences to Amazon Ads to run ads based on certain attributes & audiences defined in Segment, like the people who have visited your site. This destination is maintained by Segment. For any issues with the destination, [contact the Segment Support team](mailto:friends@segment.com). ## Getting started ### Add the destination to your Engage Space. 1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog) search for "Amazon Ads DSP and AMC". 2. Select Amazon Ads DSP and AMC and click **Add Destination**. 3. Select the **Engage Space** you'd like to add the destination to. 4. Once added, view and input the settings you'd need to complete to configure the destination. * **Connection**: Click **Connect to Amazon Ads DSP and AMC** to authenticate your destination with Amazon. * **Region**: Select the Amazon Region to deliver data to: NA, EU, or FE. * **Enable the destination**: Switch the toggle to on to enable your destination. ### Connect your Engage Audience(s) to the destination 1. Navigate to the desired Audience in Engage, and select **Add Destination**. 2. Select the **Amazon Ads DSP and AMC** destination you just created. 3. After adding your destination to the Engage audience, click on the destination from the audience page to view and complete the [audience-specific settings](https://advertising.amazon.com/API/docs/en-us/amc-advertiser-audience#tag/Audience-Metadata). * **Advertiser ID**: * [**Country Code**](https://advertising.amazon.com/API/docs/en-us/guides/amazon-marketing-cloud/audiences/audience-management-service#country-code): A 2-character string in the ISO 3166 format that will be applied for all records within the audience. * (Optional) **CPM Cents**: Cost per thousand impressions (CPM), in cents. For example, $1.00 = 100 cents. * (Optional) **Currency**: * **Description**: The audience description. Must be an alphanumeric, non-null string between 0 to 1000 characters in length. * **External Audience ID**: The user-defined audience identifier. This should be a unique, user-defined audience identifier (For example., "audience-id-for-device"). * **TTL**: Time-to-live, in seconds. The amount of time the record is associated with the audience. Values allowed are 0 .. 34300800 (For example, 2592000 for 30 days, 34300800 for 397 days). ### Configure your mappings 1. Click on the destination from the audience page, and navigate to **Matching Mappings** from the destination side view. 2. Click **Add mapping**. 3. Configure the mapping fields. 4. Save and enable the mapping. 5. When Segment computes the audience, you can see the created audience and records delivered to Amazon. ## Destination Settings | Field | Description | Required | Type | | ------ | ------------------------------------------- | -------- | ------ | | Region | Region for API Endpoint, either NA, EU, FE. | Yes | select | ## Available Actions Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Amazon Ads DSP and AMC-supported actions: > \[!NOTE] > > Individual destination instances have support a maximum of 50 mappings. * [Sync Audiences to DSP](#sync-audiences-to-dsp) ### Sync Audiences to DSP Sync audiences from Segment to Amazon Ads Audience. Sync Audiences to DSP is a **Cloud** action. The default Trigger is `event = "Audience Entered" or event = "Audience Exited"` | Field | Description | Required | Type | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | | External User ID | This is an external user identifier defined by data providers. | Yes | STRING | | Email | User email address. If not hashed, Segment will hash this value. | No | STRING | | First name | User first name. If not hashed, Segment will hash this value. | No | STRING | | Last name | User Last name. If not hashed, Segment will hash this value. | No | STRING | | Phone | Phone Number. If not hashed, Segment will hash this value. | No | STRING | | Postal | Postal Code. If not hashed, Segment will hash this value. | No | STRING | | State | State Code. If not hashed, Segment will hash this value. | No | STRING | | City | City name. If not hashed, Segment will hash this value. | No | STRING | | Address | Address Code. If not hashed, Segment will hash this value. | No | STRING | | Consent | Describes consent given by the user for advertising purposes. For EU advertisers, it is required to provide one of Geo ipAddress, amazonConsent, tcf, or gpp. | No | OBJECT | | Enable Batching | When enabled,segment will send data in batching | Yes | BOOLEAN | | Batch Size | Maximum number of events to include in each batch. Actual batch sizes may be lower. Minimum value is 1500 and maximum is 10000. | No | NUMBER | ## Engage You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo). For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`. When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync. > \[!NOTE] > > Real-time audience syncs to Amazon Ads DSP and AMC may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected. ## Settings Segment lets you change these destination settings from the Segment app without having to touch any code. | Field | Description | Required | Type | | ------ | ------------------------------------------- | -------- | ------ | | Region | Region for API Endpoint, either NA, EU, FE. | Yes | select |