> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/consent-management/setup-guides/tag-manager/amazon-consent-signal.md).

# Amazon Consent Signal

### How to use the Amazon Consent Mode feature ? <a href="#how-to-use-the-google-consent-mode-feature" id="how-to-use-the-google-consent-mode-feature"></a>

{% hint style="info" %}
Before getting started: **Amazon Consent requires activation of geolocation API**. Ask your consultant or to our support team to get an activation token for your Site ID
{% endhint %}

#### 1- Activate the feature on your workspace <a href="#id-1-activate-the-feature-on-your-workspace" id="id-1-activate-the-feature-on-your-workspace"></a>

Login on[ your workspace](https://app.commandersact.com/) Go on page `Data Governance > Consent Management > Settings` Turn **On** the option Amazon Consent Mode. The sub-menu "Amazon Consent Mode settings" will appear

<figure><img src="/files/8Qzk1MtBA1ruucQ4HVQ1" alt=""><figcaption></figcaption></figure>

#### 2-Configure your settings <a href="#id-2-configure-your-settings" id="id-2-configure-your-settings"></a>

**Categories**

Select your appropriate Privacy category from the drop-down list for each Amazon's category.

<figure><img src="/files/fBP8yKHJ2PFAMbqhzn3p" alt=""><figcaption></figcaption></figure>

#### 3-Regenerate and deploy your CMP banner(s)

You're ready to regenerate your privacy banner(s) and deploy them in production

<figure><img src="/files/JRpujZhGbpLjr5Yaq6NI" alt=""><figcaption></figcaption></figure>

Once it's deployed, our CMP will send the Consent Signal as expected by Amazon.

In your Web Container, you can remove your privacy rules of your Amazon client side tags, the Amazon Consent Signal replace the privacy rules.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.commandersact.com/features/consent-management/setup-guides/tag-manager/amazon-consent-signal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.