Additional Consent Mode (ACM)

ATP vendor IDs, ACM consent strings, and Google Ads requirements.

Additional Consent Mode (ACM) extends Google Consent Mode for ads partners that require explicit ATP vendor consent.

Overview

ACM produces an addtl_consent string listing which Google ATP vendors the user allowed. CookieShift helps you configure vendor IDs and preview the string before publish.

Why it matters

Google Ads and certain programmatic partners expect a valid ACM string in EEA/UK traffic. Missing or malformed strings can limit ad delivery or fail compliance checks.

Setup

  1. Open Consent Setup → Google Additional Consent.
  2. Enter ATP vendor IDs your legal team approved (comma-separated).
  3. Use the Preview panel to validate the generated string.
  4. Enable marketing consent category mapping so users can grant ads partners.
  5. Publish the banner and verify in browser devtools: googletag.pubads().getTargeting('addtl_consent') or network payloads.

Examples

89~733~804

Represents granted consent for vendors 89, 733, and 804 when the user accepts marketing.

Troubleshooting

  • Empty ACM string — User has not accepted marketing; or vendor list empty.
  • Ads still blocked — Confirm Google Consent Mode v2 defaults and updates fire.
  • Invalid vendor ID — Cross-check IDs against Google’s ATP vendor list for your region.

Best practices

  • Maintain vendor IDs in a spreadsheet reviewed by counsel.
  • Re-preview after every banner or category change.
  • Document ATP list in your privacy policy annex.