Amazon Consent Signal (ACS) Integration Guide
This integration allows Shopify merchants using Amazon Ads to communicate user privacy choices directly to Amazon, ensuring your advertising remains compliant and effective in the UK and EEA.
What is Amazon Consent Signal (ACS)?
Amazon Consent Signal (ACS) is Amazon’s dedicated framework for managing user consent, similar to Google Consent Mode. It enables advertisers to transmit end-user privacy choices to Amazon Ads services (such as Amazon DSP or Amazon Marketing Cloud).
By sharing a valid consent signal and the country code where consent was granted, you ensure that:
- Measurement remains uninterrupted: Amazon can accurately attribute conversions while respecting privacy.
- Targeting is compliant: Your ads reach the right audience based on their explicit consent.
- Data Quality is maintained: Only valid user data flows into your Amazon Ads dashboard.
How it Works
The ACS integration uses two specific signals to communicate consent to Amazon:
amzn_user_data: Indicates if the user allows Amazon to process personal data (like advertising IDs) for advertising.amzn_ad_storage: Indicates if the user allows Amazon to read/write advertising cookies or similar technologies on their device.
In the Pandectes GDPR Compliance app, these signals are automatically mapped to the Marketing consent category. When a visitor grants consent for Marketing, these signals are set to GRANTED. If they decline, they are set to DENIED.
Benefits for Your Store
- Avoid Service Disruption: Amazon requires a valid consent signal for campaigns running in the UK and EEA. This integration keeps your ads running smoothly.
- Enhanced Performance: Access deeper measurement and attribution benefits within Amazon Marketing Cloud (AMC).
- Built-in Trust: Showing users that you respect their privacy choices builds long-term brand credibility, essential for large retailers.
How to Enable ACS in Pandectes
Enabling the Amazon Consent Signal is straightforward and can be done directly within your Pandectes dashboard.
1. Enable the Integration
- Go to the Settings tab in your Pandectes GDPR Compliance app.
- Navigate to the Integrations section.
- Locate Amazon Consent Signal and toggle it to Enabled.
- Click Save.
2. Technical Note: WAF and Cookies
When ACS is enabled, the integration stores a first-party cookie (typically named amzn_consent).
- Note for advanced users: If you use a high-level Web Application Firewall (WAF), ensure it is configured to allow the
amzn_consentcookie format to prevent any blocking of the signal.
How to Verify and Debug your Amazon Consent Signal
After enabling the integration, you can verify that the signals are being sent correctly to Amazon Ads by inspecting your browser's cookies. This ensures your store remains compliant while allowing Amazon to process data for those who have consented.
1. Open your Browser Developer Tools
- Go to your storefront in a Chrome Incognito window (to ensure a fresh session).
- Accept the "Marketing" cookies in your Pandectes banner.
- Right-click anywhere on the page and select Inspect, then navigate to the Application tab.
2. Check the Cookies
In the left-hand sidebar under Storage, click on Cookies and select your store's URL. Look for the following indicator:
The amzn_consent Cookie (The Logic)
This is the most important cookie. It contains the raw signal sent to Amazon.
- What to look for: A URL-encoded string.
- The Proof: If you decode this value (or look at the raw string), you should see
"amznAdStorage":"GRANTED"and"amznUserData":"GRANTED". It will also show yourcountryCode(e.g., "GR" or "UK") based on your current location.
3. Common Troubleshooting Tips
- Cookie not appearing? Ensure you have clicked "Accept" on the banner and that "Marketing" cookies are enabled in your Pandectes settings.
- Wrong Country Code? The
amzn_consentcookie uses IP-based geo-detection. If you are using a VPN, the country code in the cookie will reflect the VPN location, not your physical location. - WAF Blocking: If you use a high-security firewall (like Cloudflare), ensure it isn't stripping the
amzn_consentcookie due to its JSON-like structure.
Updated on: 01/04/2026
Thank you!
