For the complete documentation index, see llms.txt. This page is also available as Markdown.

Consent management

What to set in the consent fields of the Amazon Ads connectors, and what Amazon does with the signal.

When you send user data to Amazon Ads, you must be able to show that consent was collected, stored and transmitted with it. Amazon carries that status in a dedicated framework, the Amazon Consent Signal (ACS).

These rules apply to both Amazon Ads connectors.

Connector

Relies exclusively on the Amazon Consent Signal.

Relies exclusively on the Amazon Consent Signal.

The Amazon Consent Signal is a standardised format for transmitting a user's consent preferences to Amazon Ads. It indicates whether the user consented to:

  • the use of their personal data for advertising;

  • the storage and use of advertising identifiers, such as cookies.

It is required when sending data to Amazon Ads in regulated regions, including the EEA and the UK.

The two parameters

Parameter
What it covers
Values

amzn_user_data

Consent for processing personal data for advertising.

GRANTED / DENIED

amzn_ad_storage

Consent for storing or accessing advertising data, such as cookies.

GRANTED / DENIED / NULL

  • GRANTED - Amazon can use the data for advertising purposes.

  • DENIED - the data will not be used, and may be rejected by Amazon systems.

  • NULL - the consent does not apply to the data.

In the platform, Amazon consent is set per feed, and must reflect whether the user granted permission for advertising data processing and for advertising storage.

What each connector does with it

Amazon DSP

The platform sends the user data together with the Amazon Consent Signal. Only users whose consent is GRANTED are eligible for:

  • audience targeting;

  • retargeting;

  • lookalike modelling.

Users without consent are excluded from activation automatically.

Amazon Ads Data Manager

Consent is attached to every exported record, and Amazon validates the signal before processing.

  • GRANTED - the data can be used for analytics, measurement and activation.

  • DENIED - the records are rejected or ignored by Amazon systems.

Important considerations

Consent must be collected upstream. The platform does not collect consent itself. Make sure it is captured through your consent management platform, and that the consent value is filled in on the feed configuration before you activate.

Only consented data is usable. Amazon filters strictly: data without consent is ignored, and data with denied consent cannot be used for advertising.

Best practices

  • Centralise consent management. Use a consent management platform so capture and storage stay consistent.

  • Validate the consent choice before activation, not after.

  • Align with regions. Make sure your consent collection logic accounts for the regulations that apply where your users are.

FAQ

Both of them. Amazon DSP and Amazon Ads Data Manager rely exclusively on the Amazon Consent Signal.

No. Consent is collected upstream through your own consent management platform. The platform transmits the status you set on the feed.

On Amazon DSP they are excluded from activation automatically. On Amazon Ads Data Manager their records are rejected or ignored by Amazon.

When can amzn_ad_storage be NULL?

When the consent does not apply to the data being sent. amzn_user_data accepts only GRANTED or DENIED.

Partner documentation

Amazon Ads documents its own platform at https://advertising.amazon.com/API/docs. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.

Last updated

Was this helpful?