Overview
This AWS Solution helps HAQM Ads customers seamlessly upload customer signals into their HAQM Marketing Cloud (AMC) instance without dedicating IT resources to build and support the upload workflows. HAQM Ads customers have the option to upload data from their HAQM S3 or their AWS Clean Rooms collaborations. This allows HAQM Ads customers to continue optimizing their HAQM Ads campaigns within AMC while maintaining complete control of their data, as signals are encrypted, transferred, and normalized before uploading to the AMC API.
Benefits
This solution makes it easier for customers to seamlessly upload their signals into their AMC instance. An API and new user interface help customers to automate the data transformation process and define the required format prior to ingestion into AMC.
Within hours instead of weeks, advertisers and agencies can efficiently upload their signals from AWS to AMC – without having to dedicate IT resources to build and support the upload workflows.
The solution is launched in a customer’s AWS account, making sure that they maintain full control of the data that they want to share with AMC.
Technical details
You can automatically deploy this architecture using the implementation guide and the accompanying AWS CloudFormation template.
Step 1
User uploads first-party data to designated HAQM Simple Storage Service (HAQM S3) bucket or exports data from AWS Clean Rooms to the S3 bucket. Optionally, the user can designate data from the S3 bucket to an AWS Key Management Service (AWS KMS) key to decrypt and encrypt source data and its derivatives throughout the extract, transform, load (ETL) pipeline.
Step 2
User logs in with HAQM Cognito to the provided web application and obtains the authorization tokens needed to load frontend assets from HAQM S3 and backend resources from HAQM API Gateway.
Step 3
Users interact with the provided web application through an HAQM CloudFront distribution and an API Gateway endpoint. The CloudFront resource serves static website assets from HAQM S3. The API Gateway resource provides a REST API interface to an AWS Lambda resource.
Step 4
The HAQM DynamoDB resource stores system configurations, such as user-specified connection details for HAQM Marketing Cloud (AMC) instances. These configurations are inputs in the frontend web form and saved by the API handler Lambda resource. User-specified OAuth credentials are saved to AWS Secrets Manager and the programmatically-derived OAuth refresh token.
Step 5
A Lambda resource interacts with one or more AMC instances in order to create, read, update, and delete datasets.
Step 6
When users submit requests to upload data to new or existing datasets, a Lambda resource starts an AWS Glue ETL job to normalize, hash, and reformat user-specified files.
Step 7
The AWS Glue job outputs results to an S3 bucket. This event initiates a request from a Lambda resource to each user-specified AMC instance to initiate uploads of those results.
Step 8
AMC asynchronously uploads the transformed data from HAQM S3 into the advertiser’s AMC instance.
Step 1
User uploads first-party data to designated HAQM Simple Storage Service (HAQM S3) bucket or exports data from AWS Clean Rooms to the S3 bucket. Optionally, the user can designate data from the S3 bucket to an AWS Key Management Service (AWS KMS) key to decrypt and encrypt source data and its derivatives throughout the extract, transform, load (ETL) pipeline.
Step 2
User logs in with HAQM Cognito to the provided web application and obtains the authorization tokens needed to load frontend assets from HAQM S3 and backend resources from HAQM API Gateway.
Step 3
Users interact with the provided web application through an HAQM CloudFront distribution and an API Gateway endpoint. The CloudFront resource serves static website assets from HAQM S3. The API Gateway resource provides a REST API interface to an AWS Lambda resource.
Step 4
The HAQM DynamoDB resource stores system configurations, such as user-specified connection details for HAQM Marketing Cloud (AMC) instances. These configurations are inputs in the frontend web form and saved by the API handler Lambda resource. User-specified OAuth credentials are saved to AWS Secrets Manager and the programmatically-derived OAuth refresh token.
Step 5
A Lambda resource interacts with one or more AMC instances in order to create, read, update, and delete datasets.
Step 6
When users submit requests to upload data to new or existing datasets, a Lambda resource starts an AWS Glue ETL job to normalize, hash, and reformat user-specified files.
Step 7
The AWS Glue job outputs results to an S3 bucket. This event initiates a request from a Lambda resource to each user-specified AMC instance to initiate uploads of those results.
Step 8
AMC asynchronously uploads the transformed data from HAQM S3 into the advertiser’s AMC instance.
- Publish Date
Related content
Deploy a solution to store, query, analyze, and visualize data from the HAQM Marketing Cloud (AMC) application programming interface (API).
This Guidance demonstrates how to import first party data from third party sources to HAQM Simple Storage Service (HAQM S3), and then upload and query your data directly to HAQM Marketing Cloud (AMC).