> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/consent-center/google-consent-mode-vendor-settings/use-case-1-basic-use-of-vendor-consent-mode-mapping.md).

# Use Case 1 – Basic Use of Vendor Consent Mode Mapping

In this use case we look at the **basic integration** of Google Consent Mode via the **JENTIS Vendor settings**. This enables JENTIS to submit consent information to the Google Tag client side (`gtag`) based on vendor consent.

### Activating Consent Submission

To activate this optional feature, you must customize your vendors in JENTIS:

1. Navigate to **Legal Hub → Vendors** in your JENTIS account.

<figure><img src="/files/3hq6Ifh8HcXRtqZycoXG" alt=""><figcaption></figcaption></figure>

2. Select a Google-related vendor (e.g. **Google Analytics 4**, **Google Ads**) or any custom vendor.
3. Configure its **Consent Mode mapping options**.

<figure><img src="/files/6qPu02uTnPhKgqAu9Q5L" alt=""><figcaption></figcaption></figure>

Once activated, this setup will affect **all your client-side executed Google Tag libraries**, including:

* GA4
* Google Ads
* Other gtag-based services

✅ It works regardless of whether the tag was loaded by JENTIS or another system.

### The More the Merrier

Consent Mode updates can be triggered from **multiple sources**:

* Your **Consent Management Platform (CMP)**
* Your **Website** directly
* **JENTIS**

All three can submit the same consent signals to Google simultaneously.\
As long as the signals are **not contradictory** (all push “granted” or all push “denied”), there is no issue with multiple pushes.

### Vendor Settings in Detail

When editing a vendor (for example, **Google Analytics 4**), you will find options to activate individual Consent Mode strings.

#### Example Settings

If the vendor receives consent and the corresponding checkboxes are activated, JENTIS will automatically submit the matching consent signals to Google:

* **Analytics storage**
* **Ad storage**
* **Ad user data**
* **Ad personalization**

The value sent will depend on the vendor’s consent state:

* ✅ **Granted** → signal is “granted”
* ❌ **Denied** → signal is “denied”

> ⚠️ If a checkbox is not selected, JENTIS will not link this vendor’s consent status to that Consent Mode setting.

### No Linking to Google Consent Mode

If you do not wish to submit any Consent Mode information from JENTIS, simply **leave all checkboxes unticked**.

In this case:

* Consent Mode signals are not managed by JENTIS.
* JENTIS tracking and Google Consent Mode operate independently.


---

# 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.jentis.com/consent-center/google-consent-mode-vendor-settings/use-case-1-basic-use-of-vendor-consent-mode-mapping.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.