From 72d17f504b3f4bd79c75e5633ec64dce710fe63c Mon Sep 17 00:00:00 2001 From: Thomas Gilbert Date: Thu, 25 Jul 2024 11:44:18 -0400 Subject: [PATCH 1/5] add docs for amazon ads destination --- .../catalog/actions-amazon-amc/index.md | 52 +++++++++++++++++++ 1 file changed, 52 insertions(+) create mode 100644 src/connections/destinations/catalog/actions-amazon-amc/index.md diff --git a/src/connections/destinations/catalog/actions-amazon-amc/index.md b/src/connections/destinations/catalog/actions-amazon-amc/index.md new file mode 100644 index 0000000000..5ed2f43830 --- /dev/null +++ b/src/connections/destinations/catalog/actions-amazon-amc/index.md @@ -0,0 +1,52 @@ +--- +title: Amazon Ads DSP and AMC Destination +id: 66543798b2fb3cb3e9ff992c +beta: true +--- + +{% include content/plan-grid.md name="actions" %} + +[Amazon Ads](https://advertising.amazon.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} 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, such as people who have visited your site. + +This destination is maintained by Segment. For any issues with the destination, [contact our 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){:target="_blank”} 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 authenticate your destination with Amazon. +- **Region**: Select the Amazon Region to deliver data to: NA, EU, or FE. +- **Enable the 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 configured just created. +4. After adding 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){:target="_blank"}. +- **Advertiser ID** +- [**Country Code**](https://advertising.amazon.com/API/docs/en-us/guides/amazon-marketing-cloud/audiences/audience-management-service#country-code){:target="_blank"}: A 2-character string in the ISO 3166 format that will be applied for all records within the audience. https://www.iso.org/obp/ui/#search +- (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 (e.g., "audience-id-for-device"). +- **TTL**: Time-to-live in seconds. The amount of time the record is associated with the audience. + - Values allowed: [0 .. 34300800 ] (e.g., 2592000 for 30 days, 34300800 for 397 days). +{% include components/actions-fields.html %} + +### 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. Complete! When the audience is computed in Segment, you will see the audience created and records delivered to Amazon. + +{% include components/actions-fields.html %} + From 4a6922477bfcb9e2fb97bcc1dc318eb7ef6c1760 Mon Sep 17 00:00:00 2001 From: Thomas Gilbert Date: Thu, 25 Jul 2024 11:49:28 -0400 Subject: [PATCH 2/5] add slug override --- src/_data/catalog/slugs.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/_data/catalog/slugs.yml b/src/_data/catalog/slugs.yml index ac7d784cda..4a649f29c3 100644 --- a/src/_data/catalog/slugs.yml +++ b/src/_data/catalog/slugs.yml @@ -225,4 +225,6 @@ destinations: override: "actions-xtremepush" - original: "metricstory" override: "convertly" + - original: "amazon-ads-dsp-and-amc" + override: "actions-amazon-amc" From c8209bcc1f61cec409b8da87b0c033eb59376c30 Mon Sep 17 00:00:00 2001 From: Thomas Gilbert <64277654+tcgilbert@users.noreply.github.com> Date: Thu, 25 Jul 2024 12:24:00 -0400 Subject: [PATCH 3/5] Apply suggestions from code review Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- .../catalog/actions-amazon-amc/index.md | 44 +++++++++---------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/src/connections/destinations/catalog/actions-amazon-amc/index.md b/src/connections/destinations/catalog/actions-amazon-amc/index.md index 5ed2f43830..39624059cc 100644 --- a/src/connections/destinations/catalog/actions-amazon-amc/index.md +++ b/src/connections/destinations/catalog/actions-amazon-amc/index.md @@ -8,9 +8,9 @@ beta: true [Amazon Ads](https://advertising.amazon.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} 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, such as people who have visited your site. +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 our Support team](mailto:friends@segment.com). +This destination is maintained by Segment. For any issues with the destination, [contact the Segment Support team](mailto:friends@segment.com). ## Getting started @@ -21,29 +21,29 @@ This destination is maintained by Segment. For any issues with the destination, 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 authenticate your destination with Amazon. -- **Region**: Select the Amazon Region to deliver data to: NA, EU, or FE. -- **Enable the 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 configured just created. -4. After adding 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){:target="_blank"}. -- **Advertiser ID** -- [**Country Code**](https://advertising.amazon.com/API/docs/en-us/guides/amazon-marketing-cloud/audiences/audience-management-service#country-code){:target="_blank"}: A 2-character string in the ISO 3166 format that will be applied for all records within the audience. https://www.iso.org/obp/ui/#search -- (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 (e.g., "audience-id-for-device"). -- **TTL**: Time-to-live in seconds. The amount of time the record is associated with the audience. - - Values allowed: [0 .. 34300800 ] (e.g., 2592000 for 30 days, 34300800 for 397 days). + - **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. +4. 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){:target="_blank"}. + - **Advertiser ID**: + - [**Country Code**](https://advertising.amazon.com/API/docs/en-us/guides/amazon-marketing-cloud/audiences/audience-management-service#country-code){:target="_blank"}: 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). + {% include components/actions-fields.html %} -### Configure your Mappings +### 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". +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. Complete! When the audience is computed in Segment, you will see the audience created and records delivered to Amazon. From 239b0ab0e06a93bd057813d7ecaa9eac399aedae Mon Sep 17 00:00:00 2001 From: Thomas Gilbert <64277654+tcgilbert@users.noreply.github.com> Date: Thu, 25 Jul 2024 12:24:55 -0400 Subject: [PATCH 4/5] remove duplicate snippet --- .../destinations/catalog/actions-amazon-amc/index.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/src/connections/destinations/catalog/actions-amazon-amc/index.md b/src/connections/destinations/catalog/actions-amazon-amc/index.md index 39624059cc..7361d55745 100644 --- a/src/connections/destinations/catalog/actions-amazon-amc/index.md +++ b/src/connections/destinations/catalog/actions-amazon-amc/index.md @@ -16,7 +16,6 @@ This destination is maintained by Segment. For any issues with the destination, ### Add the destination to your **Engage Space**. - 1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} 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. @@ -38,8 +37,6 @@ This destination is maintained by Segment. For any issues with the destination, - **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). -{% include components/actions-fields.html %} - ### Configure your mappings 1. Click on the destination from the audience page, and navigate to **Matching Mappings** from the destination side view. From 79f496c8935b10203d2435bd469f75e3d92ed0ff Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 25 Jul 2024 13:43:02 -0400 Subject: [PATCH 5/5] Apply suggestions from code review --- .../destinations/catalog/actions-amazon-amc/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/actions-amazon-amc/index.md b/src/connections/destinations/catalog/actions-amazon-amc/index.md index 7361d55745..9994573603 100644 --- a/src/connections/destinations/catalog/actions-amazon-amc/index.md +++ b/src/connections/destinations/catalog/actions-amazon-amc/index.md @@ -14,7 +14,7 @@ This destination is maintained by Segment. For any issues with the destination, ## Getting started -### Add the destination to your **Engage Space**. +### Add the destination to your Engage Space. 1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Amazon Ads DSP and AMC". 2. Select Amazon Ads DSP and AMC and click **Add Destination**. @@ -43,7 +43,7 @@ This destination is maintained by Segment. For any issues with the destination, 2. Click **Add mapping**. 3. Configure the mapping fields. 4. Save and enable the mapping. -5. Complete! When the audience is computed in Segment, you will see the audience created and records delivered to Amazon. +5. When Segment computes the audience, you can see the created audience and records delivered to Amazon. {% include components/actions-fields.html %}