-
Notifications
You must be signed in to change notification settings - Fork 380
Add docs for amazon ads destination #6855
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
52 changes: 52 additions & 0 deletions
52
src/connections/destinations/catalog/actions-amazon-amc/index.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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:[email protected]). | ||
tcgilbert marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
## Getting started | ||
|
||
### Add the destination to your **Engage Space**. | ||
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
|
||
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** | ||
tcgilbert marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
### Connect your Engage Audience(s) to the destination. | ||
tcgilbert marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
1. Navigate to the desired Audience in Engage, and select "Add Destination". | ||
tcgilbert marked this conversation as resolved.
Show resolved
Hide resolved
|
||
2. Select the "Amazon Ads DSP and AMC" destination you configured just created. | ||
tcgilbert marked this conversation as resolved.
Show resolved
Hide resolved
|
||
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"}. | ||
tcgilbert marked this conversation as resolved.
Show resolved
Hide resolved
|
||
- **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). | ||
tcgilbert marked this conversation as resolved.
Show resolved
Hide resolved
|
||
{% include components/actions-fields.html %} | ||
tcgilbert marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
### Configure your Mappings | ||
tcgilbert marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
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. | ||
tcgilbert marked this conversation as resolved.
Show resolved
Hide resolved
forstisabella marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
{% include components/actions-fields.html %} | ||
tcgilbert marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.