bprocks

no worries sounds like you have a different problem then if you’re not using the subdomain consent grouping.

If your really just targeting one domain then you gotta make sure your domain is entered exactly correctly in the Quantcast frontend. So if your site is on domain:

‘www.mysite.com’

then make sure that is the site property you entered and that the user is always on that domain. ie: if the user sees in their browser: mysite.com then it won’t work and you get a 403 as well ??

• This reply was modified 4 years, 1 month ago by bprocks.

search your GTM tag code for:

var host = window.location.hostname;

There will be two occurrences of it. Change it to the value seen for that var in the “Get Tag” option for your site (ie: mysite.com without the www when you’re wanting it to apply to your subdomains). So changing both to:

var host = “mysite.com”;

Note this was caused by using the “Apply to all my subdomains?” and “a group of your sites” consent scope where the GTM code needs to be modified for those two host vars mentioned above.

I figured this out in my case. I was using the GTM container code provided by Quantcast which sets the host var twice. I had updated the first reference to the subdomain tag value however half way down the script you need to change it there as well.

Getting this as well once subdomains and same site grouping is activated and the json is called from one of the sites subdomains. Did anyone manage to figure it out?

FYI: for those interested in this it was fixed in yesterdays release v15:

https://help.quantcast.com/hc/en-us/articles/360047357574-Quantcast-Choice-Code-Release-Notes-TCF-v2-0-

fyi: I managed to find a workaround for this by switching the layout type from “Use Stacks” to “Use Purposes”

Also the same with the Quantcast site itself:

https://www.quantcast.com/gdpr/consent-management-solution/

no popup when using IE11