Skip to content

Documentation

Amazon Consent Signal (ACS)

Amazon Consent Signal (ACS)

Pro Plan

Last updated Mar 29, 2026

Pro Plan Feature

This feature is available on the Pro plan and above. View pricing →

Amazon Consent Signal (ACS) is Amazon's consent framework for transmitting user privacy choices to Amazon Ads. If you run Amazon advertising campaigns targeting users in the UK or EEA, you must share a valid consent signal with Amazon Ads.

Kukie's ACS integration automatically sends consent signals to Amazon by setting the amzn_consent cookie on your site. Amazon Ads reads this cookie to determine whether it can process user data and set advertising cookies.

Availability: Amazon Consent Signal is available on Pro and Business plans.

How it works

When ACS is enabled, Kukie manages two consent parameters:

ParameterDescriptionMapped to
amzn_user_dataWhether the user consents to Amazon processing personal data for advertisingMarketing category
amzn_ad_storageWhether the user consents to Amazon reading/writing advertising cookiesMarketing category

Both parameters are mapped to the marketing cookie category. When a visitor accepts the marketing category, both signals are set to GRANTED. When they decline, both are set to DENIED.

Consent modelDefault stateAfter consent
Opt-in (EU/EEA)Both DENIEDGRANTED if marketing accepted
Opt-out (CCPA)Both GRANTEDDENIED if user opts out
Notice onlyBoth GRANTEDStays GRANTED

When ACS is enabled, Kukie sets a first-party cookie called amzn_consent on your domain. The cookie contains a JSON payload with:

  • The user's country code (detected automatically by Kukie)
  • Consent status for amznAdStorage and amznUserData
  • A timestamp of when consent was given
  • The ACS format version

Amazon Ads tags on your site read this cookie automatically to adjust their data collection behaviour.

WAF note: If your site uses a Web Application Firewall, you may need to whitelist the amzn_consent cookie format to prevent it from being blocked.

Enabling Amazon Consent Signal

  1. Go to your site's Banner Editor
  2. Open the Integrations tab
  3. Toggle on Amazon Consent Signal (ACS)
  4. Save your banner configuration

That's it. Kukie will automatically set the amzn_consent cookie based on your visitors' consent choices.

Prerequisite: Amazon Ads tags (such as the Amazon pixel or Amazon Publisher Tag) must be installed separately on your site. Kukie does not inject Amazon scripts - it only transmits the consent signal via the cookie.

Testing the integration

  1. Open your site in an incognito/private browser window
  2. Open Developer Tools (F12) and go to the Application tab
  3. Under Cookies, find your domain
  4. Before interacting with the banner, look for the amzn_consent cookie - the amznAdStorage and amznUserData values should be DENIED (for opt-in consent models)
  5. Accept the cookie banner (including the marketing category)
  6. Check the amzn_consent cookie again - both values should now be GRANTED
  7. Reject cookies or revoke consent - both values should revert to DENIED

Compatibility with other integrations

Amazon Consent Signal works independently from Google Consent Mode, Microsoft UET Consent Mode, and Microsoft Clarity. You can enable any combination of these integrations without conflicts.

Troubleshooting

  • Ensure ACS is enabled in the Integrations tab and the configuration is saved
  • Check that your plan supports Amazon Consent Signal (Pro or Business)
  • If using a CDN, ensure the banner bundle has been regenerated after enabling ACS

Some Web Application Firewalls may flag the JSON-encoded cookie value. Add the amzn_consent cookie to your WAF's allowlist.

Country code is empty

The country code in the cookie comes from Kukie's geo-detection service. If geo-detection fails (e.g. due to a network timeout), the country code may be empty. Amazon Ads will still process the consent signal, but without region-specific context.

Previous

Auto-Block Scripts with Google Consent Mode v2
Was this helpful?

Listed On