> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/regulations-manager/frameworks/amazon-consent-signal-acs.md).

# Amazon Consent Signal (ACS)

{% hint style="success" %}
**Access Type**: Regulations Manager - Editor
{% endhint %}

Amazon Consent Signal (ACS) is a consent sharing format developed by Amazon that allows advertisers and other third parties to communicate end-user's privacy choices to Amazon Ads with more granularity. In this article, we will cover the following regarding implementing Amazon Consent Signal:

* [Prerequisites](#prerequisites)
* [Overview](#overview)
* [Amazon Consent Signal (ACS) consent parameters](#amazon-consent-signal-acs-consent-parameters)
* [Enable Amazon Consent Signal (ACS)](#enable-amazon-consent-signal-acs)
* [Configure Amazon Consent Signal (ACS)](#configure-amazon-consent-signal-acs)

{% hint style="warning" %}
**Note**: Didomi only supports adding Amazon Consent Signal as a framework to regulations that utilize vendor as a data collection scope
{% endhint %}

***

### Prerequisites

Before successfully enabling and utilizing Amazon Consent Signal (ACS) in your regulation, ensure that the following criteria is met:

* Amazon Ads vendor tag configured on page where GDPR consent notice is deployed

{% hint style="info" %}
Amazon Ads (IAB ID: 793) will also need to be added to the regulation to utilize Amazon Consent Signal. It will be added automatically as part of the enablement process.
{% endhint %}

### Overview

In order to communicate UK and EEA end-users' consent decision to Amazon Ads, your organization can utilize one of the following signals:

<table><thead><tr><th width="252">Signal</th><th>Description</th></tr></thead><tbody><tr><td>Transparency &#x26; Consent (TC) string</td><td><p>For regulations that leverage the <a href="/regulations-manager/frameworks/iab-tcf.md">IAB TCF</a> framework, Amazon Ads (IAB vendor: 793) will act as a registered IAB TCF vendor and read the end-user's consent decisions directly from the TC string.</p><div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Note</strong>: If your regulation leverages the IAB TCF framework, you do not need to enable the Amazon Consent Signal (ACS) framework too since Amazon Ads will always read the TC string for end-user consent decisions.</p></div></td></tr><tr><td>Amazon Consent Signal (ACS)</td><td>For regulations that do not leverage the IAB TCF framework, Amazon Ads will rely on the Amazon Consent Signal (ACS) to determine the end-user's consent decisions.</td></tr></tbody></table>

The steps below provide an overview of the configuration and consent signaling flow for the Amazon Consent Signal (ACS).

{% stepper %}
{% step %}
Enable and configure Amazon Consent Signal (ACS) on Didomi regulation
{% endstep %}

{% step %}
Deploy privacy flow on website that utilizes the regulation
{% endstep %}

{% step %}
End-user provides consent decisions on the website
{% endstep %}

{% step %}
Didomi calculates and shares the end-user's consent decision with Amazon Consent Signal (ACS)
{% endstep %}

{% step %}
Amazon Consent Signal (ACS) communicates consent signals to Amazon Ads so that ads comply with end-user consent decisions
{% endstep %}
{% endstepper %}

### Amazon Consent Signal (ACS) consent parameters

The Amazon Consent Signal (ACS) is comprised of two consent parameters: `amzn_user_data` and `amzn_ad_storage` . Refer to the table below for more information on these parameters.

<table><thead><tr><th width="176">Consent parameter</th><th width="162">Values</th><th>Description</th></tr></thead><tbody><tr><td><code>amzn_user_data</code></td><td><code>GRANTED</code> | <code>DENIED</code></td><td>Indicates whether end-user has consented to Amazon processing personal data (e.g. advertising identifier) for advertising purposes</td></tr><tr><td><code>amzn_ad_storage</code></td><td><code>GRANTED</code> | <code>DENIED</code></td><td>Indicates whether end-user has given Amazon consent to read or write advertising cookies or similar technologies on the end-user's device</td></tr></tbody></table>

{% hint style="info" %}
The default value for both `amzn_user_data` and `amzn_ad_storage` is set to `DENIED` unless otherwise configured through the Didomi console.
{% endhint %}

Didomi determines the value of the Amazon Consent Signal (ACS) consent parameters by utilizing the end-user's consent decisions for the **Amazon Ads** vendor (IAB ID: 793). In order for Didomi to set the consent parameters to `GRANTED` , the Amazon Ads vendor must receive global consent (consent for the vendor and all of its purposes) from the end-user.

<table><thead><tr><th width="178.4166259765625">Consent parameter</th><th width="100.666748046875">Value</th><th>End-user consent decision</th></tr></thead><tbody><tr><td><code>amzn_user_data</code></td><td><code>GRANTED</code></td><td>End-user provides global consent (consent for vendor all of its purposes) for Amazon Ads vendor (IAB: 793) </td></tr><tr><td><code>amzn_ad_storage</code></td><td><code>GRANTED</code> </td><td>End-user provides global consent (consent for vendor all of its purposes) for Amazon Ads vendor (IAB: 793) </td></tr></tbody></table>

If global consent is not received for the Amazon Ads vendor (IAB ID: 793), both consent parameters will have a value of `DENIED` .

<table><thead><tr><th width="178.4166259765625">Consent parameter</th><th width="100.666748046875">Value</th><th>End-user consent decision</th></tr></thead><tbody><tr><td><code>amzn_user_data</code></td><td><code>DENIED</code></td><td>End-user did not consent to one or more purposes for Amazon Ads vendor (IAB: 793) or the vendor itself</td></tr><tr><td><code>amzn_ad_storage</code></td><td><code>DENIED</code> </td><td>End-user did not consent to one or more purposes for Amazon Ads vendor (IAB: 793) or the vendor itself</td></tr></tbody></table>

### Enable Amazon Consent Signal (ACS)

In order to enable the Amazon Consent Signal (ACS) on a regulation, click **Regulations Manager** in the left-hand panel.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2F8mHBFEasbCecBPmuE3Kh%2FScreenshot%202026-09-15%20at%207.21.21%E2%80%AFAM.png?alt=media&amp;token=a1e5ea20-451e-42c6-8322-459932ce64af" alt="" width="563"><figcaption></figcaption></figure>

Navigate to a regulation that uses vendor as a data collection scope on the subsequent list and click the edit icon inline with the regulation name.

{% hint style="warning" %}
**Note**: Didomi only supports adding Amazon Consent Signal as a framework to regulations that utilize vendor as a data collection scope
{% endhint %}

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FDVUJujsyYOYNbRKbfMCt%2FScreenshot%202026-09-16%20at%2010.03.46%E2%80%AFAM.png?alt=media&amp;token=79218c9e-559a-4f81-9bda-2854612bd230" alt="" width="563"><figcaption></figcaption></figure>

Ensure that the **Global settings** tab is selected and navigate to the ***Frameworks*** section. Enable the toggle inline with **Amazon Consent Signal**.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FTfSaYYzNHrbpdpNwW9R9%2FScreenshot%202026-09-16%20at%2010.06.36%E2%80%AFAM.png?alt=media&amp;token=1933c846-58e8-4b6f-83e0-85d493a30cef" alt="" width="563"><figcaption></figcaption></figure>

By enabling the Amazon Consent Signal framework on the regulation, Didomi will automatically add Amazon Ads (IAB: 793) to the list of vendors for the regulation.

### Configure Amazon Consent Signal (ACS)

{% hint style="info" %}
The default value for both `amzn_user_data` and `amzn_ad_storage` is set to `DENIED` unless otherwise configured through the Didomi console. The following steps are optional and should only be used if your organization intends to override the default value of the the consent parameters within the Amazon Consent Signal (ACS).
{% endhint %}

With Amazon Consent Signal (ACS) added as a framework to the regulation, select the **Frameworks** tab and expand the **Amazon Consent Signal** accordion.&#x20;

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FDd3VomBWR55Ph9jNgKDU%2FScreenshot%202026-09-16%20at%2010.10.04%E2%80%AFAM.png?alt=media&amp;token=faf22116-6f17-4d1f-8599-2749aa00a975" alt="" width="563"><figcaption></figcaption></figure>

If necessary, use the following toggles in the accordion to edit the following:

<table><thead><tr><th width="321.7332763671875">Toggle</th><th>Description</th></tr></thead><tbody><tr><td>Set the default status of Amazon consent signals when the page loads</td><td>Required to override the default status of <code>amzn_ad_storage</code> and/or <code>amzn_user_data</code> </td></tr><tr><td>Enable <strong>Ad storage</strong> before the user gives consent</td><td>Overrides the default value of <code>amazn_ad_storage</code> and sets the default to <code>GRANTED</code></td></tr><tr><td>Enable <strong>Ad user data</strong> before the user gives consent</td><td>Overrides the default value of <code>amazn_user_data</code> and sets the default to <code>GRANTED</code></td></tr></tbody></table>

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FQXdVfF7XFmEyn5GB5BVn%2FScreenshot%202026-09-16%20at%2010.15.13%E2%80%AFAM.png?alt=media&amp;token=5340302a-eba5-4c98-a567-90a92e734f80" alt="" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.didomi.io/regulations-manager/frameworks/amazon-consent-signal-acs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.