# Google Tag Manager is firing both region consents

**URL:** <https://forum.finsweet.com/t/google-tag-manager-is-firing-both-region-consents/7474>\
**Category:** Consent Pro\
**Tags:** consent-pro-v2\
**Created:** [August 3, 2026, 12:43pm UTC](https://forum.finsweet.com/t/google-tag-manager-is-firing-both-region-consents/7474 "2026-08-03T12:43:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sarah1](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/sarah1/32/5162_2.png) [@sarah1](https://forum.finsweet.com/u/sarah1)\
**Post date:** [August 3, 2026, 12:43pm UTC](https://forum.finsweet.com/t/google-tag-manager-is-firing-both-region-consents/7474/1 "2026-08-03T12:43:55Z")

</div>

## Description

when the site first loads it defaults to all consent granted (1st screenshot), but immediately after that, it resets to all consent denied

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/finsweet1/original/2X/b/b0e110ff2a2390e600de6a0b26bdfa0aaf49e804.png)

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/finsweet1/original/2X/3/3c693114fad03122143a2ee829bbd99f8aaa88bb.png)

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/finsweet1/original/2X/e/e3991b4f9361ec96004196c2c424fd5f0ea34234.png)

## Site URL

**Required:** Please provide a staging/production URL where we can see the issue

- URL: [https://breezyhr.webflow.io/](https://breezyhr.webflow.io/)
- Webflow Read-only link: [Webflow - Breezy HR 2026](https://preview.webflow.com/preview/breezyhr?utm_medium=preview_link&utm_source=designer&utm_content=breezyhr&preview=cc587ffaceb7ab57dc56e3add60d39af&workflow=preview)

## Expected Behavior

the second consent for the GDPR regions should not have fired since we are in the US, its granting our consents then a second later denying them.

---

<div class="post-metadata">

**Author:** ![jesse.muiruri](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/jesse.muiruri/32/6611_2.png) [@jesse.muiruri](https://forum.finsweet.com/u/jesse.muiruri)\
**Post date:** [August 3, 2026, 4:54pm UTC](https://forum.finsweet.com/t/google-tag-manager-is-firing-both-region-consents/7474/2 "2026-08-03T16:54:19Z")

</div>

Hey @sarah1

The state that actually applies is what carries through from Consent Initialization `Event: Initialisation` into later events for example `Container Loaded`, not every row in the Consent Default list.  
  
Consent Pro’s GTM template registers all of your configured region defaults at init. In your setup that’s both the EU row using default `denied` and the Global row default `granted`, so Tag Assistant will show two Consent Default events. That’s expected.  
  
Only the default that matches the visitor’s region is what gets persisted. The other row is still listed because it was registered, not because it overwrote your active consent.  
  
If the visitor already has an `fs-consent` cookie state, that stored choice can also update consent after defaults are set, so the final state may come from the cookie rather than from the defaults alone.  
  
So to debug and confirm what is persisted, please check for example what the Initialization step contains in the Consent Tab

Thanks

---

<div class="post-metadata">

**Author:** ![sarah1](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/sarah1/32/5162_2.png) [@sarah1](https://forum.finsweet.com/u/sarah1)\
**Post date:** [August 3, 2026, 8:23pm UTC](https://forum.finsweet.com/t/google-tag-manager-is-firing-both-region-consents/7474/3 "2026-08-03T20:23:32Z")

</div>

Thanks @jessie.muiruri, looks like you were right, it defaults to granted and it even pushes the current state as granted on consent initialization, but then it resets twice with two more consent default events, and ends up wiping the current state and making the default state denied

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/finsweet1/original/2X/8/802530769d4fd009ebefaf116f9328551fd52a9b.png)

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/finsweet1/original/2X/e/e99607d16efd61766eb38f60684a1b436773a37a.png)

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/finsweet1/original/2X/1/1e3c3c5b703c59006a5a7a57aa5dee7a451e61f6.png)

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/finsweet1/original/2X/b/b76c35bf4bdc8dbf56377e98d37e71c56ac7341f.png)

---

<div class="post-metadata">

**Author:** ![jesse.muiruri](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/jesse.muiruri/32/6611_2.png) [@jesse.muiruri](https://forum.finsweet.com/u/jesse.muiruri)\
**Post date:** [August 5, 2026, 12:23pm UTC](https://forum.finsweet.com/t/google-tag-manager-is-firing-both-region-consents/7474/4 "2026-08-05T12:23:58Z")

</div>

Hey @sarah1

This is what devs had to say concerning what you’ve shared

> It looks correct, nothing wrong with those follow up screenshots
> 
> I believe they are still confused why the state is updated
> 
> For best interpretation, they need to focus on the consent states of `Event: Initialisation` step going forward
> 
> Anything before that is initial states that could be from their current consents or default region consents
> 
> They need to test against what is Current State shows from Event Number 6,7,8…going forward in their follow up screenshot.

Hope it makes sense, let me know, thanks
