# How to Test Google Consent Mode Is Working

> Verify your Google Consent Mode setup by checking the gcs parameter in Google Analytics collect requests, using the Consent Mode Inspector, and inspecting the dataLayer. Step-by-step guide by Secure Privacy.

- Canonical: https://support.secureprivacy.ai/article/checking-the-google-consent-mode-implementation
- Product: Consent Management
- Category: Google Consent Mode
- Published: 2026-03-06T12:44:00+00:00
- Updated: 2026-04-15T21:48:41.548+00:00
- Reading time: 5 minutes

---

**Summary:** This guide explains how to verify that [Google Consent Mode](https://developers.google.com/gtagjs/devguide/consent) is correctly implemented and working on your website using Secure Privacy. You'll learn how to identify the `gcs` **parameter** in Google Analytics network requests, compare tag behavior with and without consent, and use browser tools like the **Consent Mode Inspector** and `window.dataLayer` to confirm consent signals are firing correctly.

## Who Is This Guide For?

-   **Website administrators and developers** verifying their Google Consent Mode integration after setup
    
-   **Technical marketers and analytics managers** checking that Google Analytics and Google Ads tags respond correctly to user consent
    
-   **Compliance professionals** confirming GDPR-compliant tag behavior before go-live
    

## Before You Begin

-   Google Consent Mode must already be implemented on your site (via [Basic](https://support.secureprivacy.ai/article/google-consent-mode-basic-setup--secureprivacy-guide) or [Advanced Mode](https://support.secureprivacy.ai/article/implementing-google-consent-mode-advanced-using-google-tag-manager-community-template))
    
-   You have access to your browser's **Developer Tools** (Chrome DevTools recommended)
    
-   Your Secure Privacy consent banner is live and rendering correctly on the page
    

## How Google Consent Mode Changes Google Analytics Tag Behavior

Before testing, it helps to understand what changes once Google Consent Mode is active. By default, Google Consent Mode **blocks Google tags from creating or reading any cookies** until the user grants consent—similar to fully blocking the script, but with one key difference: a **cookieless "collect" ping is still sent** to Google Analytics.

Previously, without Consent Mode, Secure Privacy blocked the entire Google Analytics script when a user hadn't consented, meaning _no_ network requests were made. With Google Consent Mode active, a lightweight `collect` API call is sent immediately—but it contains a special `gcs` **parameter** that signals the user's consent status to Google.

### Quick Reference: `gcs` Parameter Values

-   `G100` — Consent **Denied** (default state, no cookies set)
    
-   `G101` — Analytics consent **Granted**
    
-   `G111` — All consent types **Granted**
    

## How to Check Google Consent Mode Is Working: No Consent State

To verify correct behavior before a user consents, follow these steps:

1.  Open your browser's **Developer Tools** (F12 or right-click > Inspect).
    
2.  **Clear all cookies** for the site (Application tab > Storage > Clear site data).
    
3.  Reload the page **without interacting with the consent banner**.
    
4.  Go to the **Network tab** and filter for `collect`.
    

You should see a `collect` request sent to Google Analytics. This confirms Google Consent Mode is active. Unlike a non-Consent Mode implementation, this request fires even without consent—but **no cookies are created**.

![Chrome DevTools Network tab showing a Google Analytics collect request firing without user consent under Google Consent Mode](https://pub-7bd19505838640d0a08ef1bd6ec3fb9b.r2.dev/articles/513ece74178c66db9fa3-ce0ef70af712.webp)

The Google Analytics `collect` request visible in the Network tab before user consent is given — a sign that Google Consent Mode is active.

To inspect the request in detail, click the `collect` call and review its parameters:

![Chrome DevTools showing the gcs parameter with value G100 in a Google Analytics collect request, indicating consent is denied](https://pub-7bd19505838640d0a08ef1bd6ec3fb9b.r2.dev/articles/0c8ab4193d032710256f-15e73ca3b198.webp)

The `gcs=G100` parameter in the `collect` request confirms Google Consent Mode is active and consent is currently **Denied**.

The highlighted `gcs` parameter with a value of `G100` confirms that Google Consent Mode is active and the current consent state is **Denied**. No cookies will be set in this state.

## Verifying Google Consent Mode After the User Grants Consent

Once a user provides consent via the Secure Privacy banner, Google Consent Mode updates its status to **Granted**. This triggers the following changes:

-   **Cookies are created** by Google Analytics and any other consented Google tags.
    
-   The next `collect` API request will include `gcs=G101` (analytics consent granted) or `gcs=G111` (all consent types granted).
    

![Chrome DevTools Network tab showing gcs parameter with value G111 in a Google Analytics collect request after user grants consent](https://pub-7bd19505838640d0a08ef1bd6ec3fb9b.r2.dev/articles/c22f3a4107027f7648f9-c4fc424775c7.webp)

After the user grants consent, the `gcs` parameter updates to `G101` or `G111`, confirming consent has been registered by Google Consent Mode.

**Note:** If you inspect a site _without_ Google Consent Mode, you will only see the `collect` request _after_ the user consents (when the script is loaded), and **the** `gcs` **parameter will be absent entirely**. The presence of `gcs` is your confirmation that Google Consent Mode is active.

## Faster Verification: Consent Mode Inspector Browser Extension

For a quicker visual check of consent state without digging through DevTools, use the [**Consent Mode Inspector by InfoTrust**](https://chromewebstore.google.com/detail/consent-mode-inspector-by/phpllnjdcoiijcpgcbhlocjgcegjfnhb). This Chrome extension displays the current Google Consent Mode state for all consent types at a glance directly in your browser toolbar.

![Consent Mode Inspector Chrome extension by InfoTrust showing the granted and denied status for each Google Consent Mode category](https://knowledgebasecdn.helpwise.io/uploads/234834/206059/d0a3e522f5c152e1dce33df7cd784ed552397486-1774302363-55e68b796cbb29cbc6c8d1f2eba8d853c496699f)

The Consent Mode Inspector by InfoTrust displays the live consent status for each category—a fast alternative to manual DevTools inspection.

## Verifying Consent Mode Defaults via the dataLayer

Google Consent Mode defaults and subsequent consent updates are also logged directly in the **dataLayer**. You can inspect these in your browser console by entering:

```
window.parent.dataLayer
```

This will display the full history of consent events—including the initial default consent state set by your Secure Privacy configuration and any updates triggered by user interaction with the banner.

![Browser console showing window.parent.dataLayer output with Google Consent Mode default and update events logged](https://knowledgebasecdn.helpwise.io/uploads/234834/206059/70ead91404cfbf8d3e71e60ad6ca5b169282f95e-1774303505-de1b4e78b93009ae14a0708f897e29b63a914e50)

The `window.parent.dataLayer` console output showing Google Consent Mode default state and consent update events.

## Frequently Asked Questions (FAQ)

### How do I know if Google Consent Mode is working correctly?

Open Chrome DevTools, go to the **Network tab**, and filter for `collect`. If you see a `collect` request with a `gcs` parameter present, Google Consent Mode is active. A value of `G100` means consent is denied; `G101` or `G111` means consent has been granted.

### What does the gcs parameter mean in Google Analytics?

The `gcs` parameter is added by Google Consent Mode to every `collect` API request. It indicates the current consent state: `G100` = Denied, `G101` = Analytics Granted, `G111` = All Granted. Its absence means Google Consent Mode is not implemented.

### Why do I see a collect request even when the user hasn't consented?

This is expected behavior in Google Consent Mode (especially Advanced Mode). A cookieless "collect" ping is sent to enable conversion and behavioral modeling without setting cookies or identifying the user. This is different from a standard Google Analytics implementation, which only fires after consent.

### What is the Consent Mode Inspector and how do I use it?

The [Consent Mode Inspector by InfoTrust](https://chrome.google.com/webstore/detail/consent-mode-inspector/lliiokiiffoojajeopfobmlbkpkidifb) is a free Chrome browser extension that visually displays the current Google Consent Mode state for each consent category on any page. Install it, visit your site, and click the extension icon to see a live readout of granted and denied consent states.

### How do I check consent mode events in the dataLayer?

Open your browser console and type `window.parent.dataLayer`. Look for `consent` events to see the default state set at initialization and any updates recorded after user interaction with your consent banner.

## Need Further Assistance?

For additional help verifying your Google Consent Mode implementation, contact our support team at [support@secureprivacy.ai](mailto:support@secureprivacy.ai).

For **urgent or systemic escalations related to Google Consent Mode**, contact our designated point of contact: [**Andrew Sidorkin**](mailto:andrew@secureprivacy.ai). We aim to address all escalations **within one business day.**

For policy questions directed to Google, contact the Google EU User Consent Policy team at [ddp-gdpr-escalations@google.com](mailto:ddp-gdpr-escalations@google.com).