> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/integrations/google/configure-google-additional-consent-mode-web.md).

# Configure Google Additional Consent Mode (web)

[Google's Additional Consent Mode](https://support.google.com/admanager/answer/9681920?hl=en) allows collecting and passing consent information for [Google's Ad Technology Providers](https://support.google.com/admanager/answer/9012903) that do not support the IAB TCF.

### Configuration

#### Configure your Google account 

In your [Google Ad Manager](https://support.google.com/admanager/answer/7673898), [AdSense](https://support.google.com/adsense/answer/7670013), or [AdMob](https://support.google.com/admob/answer/7666519) account, configure the ad technology providers that you work with.

<img src="/files/6seW0ZkQwlAxsTHHy5Ig" alt="" width="563">

#### Configure your Didomi account

1. In your Didomi Console, select the corresponding vendors with the Google flag for your consent notices:<br>

   <figure><img src="https://p59.f1.n0.cdn.getcloudapp.com/items/geugRZE0/e95ef08f-d0f1-47db-8aab-12601f0cace4.jpeg?v=d1ca9e6738d7f92d9d7659bfec032325" alt="" width="563"><figcaption></figcaption></figure>
2. If your account was created before around summer 2023, you might see this box in the 2.Customization - Integrations section. Make sure that the "Use a standard list of ATP vendors" checkbox is unchecked for the Additional Consent Mode Integration :\
   \
   For newer accounts, this box is not available, you can proceed to the next step directly.

   <figure><img src="https://p59.f1.n0.cdn.getcloudapp.com/items/rRujgAvw/916c1821-d75a-42ca-b766-5b0bbe1b8d97.jpeg?v=87d225fd09f520c7d0a39aa2c7617159" alt="" width="563"><figcaption></figcaption></figure>
3. Publish your consent notice after making those changes.

#### Validation

To validate the integration:

1. Go to your website.
2. Give consent.
3. Open up the Developer Tools of your browser.
4. Go to the Network tab.
5. Identify ad requests to Google (usually starting with **<https://securepubads.g.doubleclick.net/gampad/ads>** for GAM) and ensure that the addtl\_consent query-string parameter is present with your selected Google ATP vendors:

Conversely, if you do not give consent, the addtl\_consent query-string parameter should not be present in the ad request.

#### Limitations

**Standard list of ATP vendors**

* We used to support a standard list of ATP vendors without allowing selection of specific vendors. This legacy mode is enabled by checking the "Use a standard list of ATP vendors" box in the Didomi Console.
* We recommend disabling that option for new notices. For existing consent notices that have this option enabled, we recommend disabling it after configuring ATP vendors.

### Frequently asked questions

* **Can users make granular choices for Google ATP vendors?**

Yes! ATP vendors are displayed like any other vendor and users can make specific choices for them.

* **How is consent information stored for ATP vendors?**

Information regarding consent and legitimate interest for ATP partners is stored in the didomi\_token cookie. The information is encoded in a format similar to that of the TCF consent string to optimize the size of said cookie. <br>

* **Can Google's Additional Consent Mode be used when the IAB TCF is disabled?**

No. Google Additional Consent Mode is an extension of the IAB's TCF and cannot be used independently of it.

* **Is Google's Consent Mode the same feature as Google's Additional Consent mode?**

No! [Google Consent Mode](https://support.google.com/analytics/answer/9976101?hl=en) is a separate feature not related to the IAB TCF.


---

# 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://docs.didomi.io/integrations/google/configure-google-additional-consent-mode-web.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.