-
Notifications
You must be signed in to change notification settings - Fork 7
Description
To be honest, I don't know if there is even a "fix" for this β probably not. But I still open this issue in case someone is also investing 10 hours to find out why the Bing tag does not work correctly (like I did π ).
So basically, we use a setup for some clients where we have 2 tags of this consent tag in the same container, 1 for all EEA countries with all consents set to denied by default, and 1 tag for Switzerland where consent is set to granted by default.
For Google's consent mode this works, because the API supports including countries, like this (EEA example):
gtag("consent", "default", {
ad_storage: "denied",
analytics_storage: "denied",
ad_user_data: "denied",
ad_personalization: "denied",
personalization_storage: "denied",
functionality_storage: "denied",
security_storage: "denied",
region: [
"AT",
"BE",
"BG",
"HR",
"CY",
"CZ",
"DK",
"EE",
"FI",
"FR",
"DE",
"GR",
"HU",
"IE",
"IT",
"LV",
"LT",
"LU",
"MT",
"NL",
"PL",
"PT",
"RO",
"SK",
"SI",
"ES",
"SE",
"NO",
"IS",
"LI"
]
})However, since Microsoft's consent mode does not support this, having 2 of these tags will "break" the setup and just use the settings which are loaded last.
I don't know what's the best workaround here. Any suggestions?