Amazon DSP: Hashed Email Overview

Amazon DSP is a demand-side platform that allows advertisers to programmatically buy display and video ads at scale. You can use Cloud Connect with Amazon DSP to leverage audiences from Lytics to improve your targeting for Amazon ads.

Note that in order to successfully export audiences to Amazon DSP, an identifier mapping must first be set up in Amazon. This document covers details for hashed emails via the Upload Hashed Identifiers workflow and exporting Audiences leveraging the Amazon DSP Audience Destination.

Note: The mapping created by the Hashed Identifier Upload must exist for 7 days before it can be used to sync a user to an audience via the Amazon DSP Destination. Additionally, SQL logic used in Cloud Connect audiences must ensure users are not included in an audience until 7 days after they've been sent in the Hashed Identifier Upload.

SQL Example:

#Hashed Identifier Upload SQL QUery

SELECT email, account_id
FROM Database1.Table1;

#Audience SQL Query

SELECT email, account_id
FROM Database1.Table1
WHERE account_created_date <= DATEADD(day,-7, GETDATE());

Amazon DSP: Upload Hashed Identifiers

Upload Hashed Identifiers creates mappings necessary to sync Cloud Connect audiences to Amazon DSP via a hashed email identifier.
Integration Details

• Implementation Type: Server-side
• Implementation Technique: REST API
• Frequency: Real-time
• Resulting data: A mapping in Amazon DSP for each user in the audience that will enable exports via the Audience Destination.

Fields

The Amazon DSP integration requires Raw (unhashed) Email as the user identifier. Any emails used in an Audience must already be included in the Hashed Identifiers Upload 

Configuration

Follow these steps to set up and configure a Hashed Identifiers Audience for Amazon DSP in Cloud Connect. If you are new to creating Audiences in Cloud Connect, see the Getting Started documentation for more information.

1. Create an audience including raw email for all users you wish to include in the email match. Once the audience is created, click Export
2. Select Amazon DSP: Upload Hashed Identifiers from the list of Destinations.
3. Select the Authorization you would like to use or create a new one.
4. Enter a Label to identify this job you are creating in Lytics.
5. (Optional) Enter a Description for further context on your job.
6. Complete the configuration steps for your job.
7. From the Profile ID input, select select the Amazon DSP Profile/region to export to.
8. (optional) From the Email Field input, select select the field name that contains the user's email. One of either Email Field or Hashed Email Field is required.
9. (optional) From the Hashed Email Field input, select the field that contains the user's email, SHA 256 hashed (before hashing, make sure to trim whitespace from input email addresses and format them lowercase, with no accents or special characters, per the Amazon documentation). One of either Email Field or Hashed Email Field is required.
10. (optional) Select the Existing Users checkbox, to select this to immediately push users who currently exist in the selected Lytics audience. Deselecting will only push users as they leave or enter the audience.
11. (Optional) Toggle Show Advanced Options.
12. (optional) From the First Name Field input, select select the field name that contains the user's first name.
13. (optional) From the Last Name Field input, select select the field name that contains the user's last name.
14. (optional) From the User Address Field input, select select the field name that contains the user's address.
15. (optional) From the User Phone Number Field input, select select the field name that contains the user's phone number.
16. (optional) From the User City Field input, select select the field name that contains the user's city.
17. (optional) From the User State Field input, select select the field name that contains the user's state.
18. (optional) From the User Zip Field input, select select the field name that contains the user's zip code.
19. Click Complete

Amazon DSP: Export Audience

The combination of this export audience Destination with either the Upload Hashed Identifiers Destination detailed above allows you to create powerful audiences for targeting in Amazon Advertising.

Note: The mapping created by the Hashed Identifier Upload must exist for 7 days before it can be used to sync a user to an audience via the Audience Export workflow.

Integration Details

• Implementation Type: Server-side.
• Implementation Technique: REST API
• Frequency: Real-time.
• Resulting data: A Lytics audience is exported to Amazon with the prefix lytics_.

Configuration

Follow these steps to set up and configure an Audience to Amazon DSP from Cloud Connect.

1. Ensure that an Upload Hashed Identifiers Audience has been configured for the users you wish to sync, and that it has been at least 7 days since the Audience was initiated. Contact Lytics Support for assistance with correctly configuring the hashed upload workflow.
2. Create an Audience including raw email for all users you wish to target. Important: SQL logic for the audience must ensure users are not included in an audience until 7 days after they've been sent in the Hashed Identifier Upload. Once the audience is created, click Export
3. Select Amazon DSP from the list of Destinations.
4. Select the Authorization you would like to use or create a new one.
5. Enter a Label to identify this job you are creating in Lytics.
6. (Optional) Enter a Description for further context on your job.
7. Complete the configuration steps for your job.
8. From the Profile ID input, select the Amazon DSP Profile/region you wish to export to.
9. In the Advertiser ID text box, enter your Amazon DSP Advertiser ID.
10. From the Match Method input, select the match method that was used for this audience. Select Hashed Emails for audiences that have been synced via the Upload Hashed Identifiers workflow.
11. (optional) From the Email Field input, select the field that contains the user's email. One of either Email Field or Hashed Email Field is required if Match Method is set to Hashed Emails, and should match the field used in the Upload Hashed Identifiers job.
12. (optional) From the Hashed Email Field input, select the field that contains the user's email, SHA 256 hashed (prior to hashing, make sure to trim whitespace from input email addresses and format them lowercase, with no accents or special characters, per the Amazon documentation). One of either Email Field or Hashed Email Field is required if Match Method is set to Hashed Emails, and should match the field used in the Upload Hashed Identifiers job.

13. (optional) Select the Existing Users checkbox to immediately push users who currently exist in the selected Lytics audience. Deselecting will only push users as they leave or enter the audience.

14. Click Complete