Amazon ACS

The Amazon Consent Signal (ACS) tells Amazon ad tags whether they may store ad cookies and process personal data. OptSens uses Amazon's official ACS SDK to set this signal.

What OptSens does on the wire

OptSens loads Amazon's official SDK from c.amazon-adsystem.com/aat/amzn-consent.js, which exposes window.amznConsent. Both Amazon signals map from the visitor's advertising consent:

Signal	Maps to	Controls
amznAdStorage	Advertising consent	Whether Amazon may write ad cookies
amznUserData	Advertising consent	Whether Amazon may process personal data

OptSens calls the SDK builder with the consent state and, when available, the visitor country code, the TC string, and the GPP string. The SDK writes the amzn_consent cookie and fires the amznConsentChange event that Amazon tags listen for. OptSens also writes a matching first-party amzn_consent cookie as a fallback, since the SDK does not always overwrite the value on a later consent change.

The default is denied. OptSens updates the signal to granted only when the visitor consents to advertising.

Skipped in IAB TCF mode

When the page runs in IAB TCF mode, OptSens does not load the ACS SDK. The TC string already includes the Amazon vendor, and the separate signal is not needed.

How to enable it

Amazon ACS requires a Plus plan or higher.

1. Open the dashboard and select your domain.
2. Go to Frameworks.
3. Toggle Amazon Consent Signal.
4. Save.

Enable it for Amazon advertising in the EEA and UK, on pages that are not served in IAB TCF mode.

How to verify it

Open a page that is not in IAB TCF mode, accept advertising in the banner, then run this in the browser console:

document.cookie
  .split('; ')
  .find(function (c) { return c.startsWith('amzn_consent='); });

Decode the value to read the signal:

JSON.parse(decodeURIComponent(
  document.cookie.split('amzn_consent=')[1].split(';')[0]
)).amazonConsentFormat;

amznAdStorage and amznUserData should both read GRANTED after you accept, and DENIED before consent or after you reject.