Go to the Destinations overview page and click the Add destination button. Select Amazon Ads and click Continue. You can then authenticate Hightouch to Amazon Ads.
For the Authentication method, select Log in to Amazon Ads and log into your Amazon Ads account. Once successful, you will be redirected back to Hightouch to enter an advertiser ID and a descriptive name for your destination to complete setup.
Once you've set up your Amazon Ads destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Amazon Ads destination you want to sync to.
To match rows from your model to audience in Amazon Ads, you need to select a model column and corresponding Amazon Ads field. For third-party data audiences, you can match on any of the following fields:
Cookie ID
Mobile Advertising ID
External ID
For first-party data audiences, you can match on any of the following fields:
By default, Hightouch automatically hashes first-party user data fields before sending requests to Amazon Ads.
You can turn off this behavior in the sync configuration. When off, the data from the model should be appropriately normalized and hashed according to Amazon Ads' hashing requirements.
Hightouch retrieves the audience metadata from Amazon Ads in real-time. The matched number displayed in Hightouch should reflect what you see in Amazon Ads. Note that the matched numbers are approximated to maintain privacy thresholds. Hightouch takes the matched count to calculate a match rate for your sync, where applicable. The calculation breakdown:
matched_user_count / # of rows queried in the latest sync run
The match rate is
not
calculated when:
syncing to an existing segment because the total number of records to ever be uploaded to the segment is unknown
removed users from your model is not removed in Amazon Ads because the matched user count would be inflated in the calculation
Common causes for low match rates:
Your audience model is too small. Most ad platforms do not display the matched number unless there's at least one thousand matched users to maintain privacy thresholds.
The upload is still processing. We recommend waiting at least
72 hours
from the first sync run for numbers to settle.
Your data isn’t cleaned or hashed properly. Hightouch normalizes and hashes your data according to destination requirements, but it’s still good to make sure that the data is as clean as possible. Note that Hightouch cannot clean your data if you opt to hash it yourself. In that case, ensure you follow the data cleaning requirements forAmazon Ads.
To date, our customers haven't experienced any errors while using this destination. If you run into any issues, please don't hesitate to . We're here to help.
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.