From today, it seems it’s not working with Quantcast anymore! Suddenly, stop working, not euconsent-v2 cookie present!
Why is that, anyone know and there is a fix for this?
Thanks!
]]>When checking Google Chrome Developer Tools, I can see the error “USP is not accessible”.
Any idea what is going wrong and how to solve it?
]]>https://ampforwp.com/tutorials/article/how-to-add-quantcast-notice-in-amp/
Account Id: In this field, you need to enter an Account ID.
Hash Code: In this field, you need to enter Hash Code.
Could you explain in more detail where to retrive these values?
]]>The first is an Uncaught TypeError with the cmp.js file, which returns the following:
TypeError: n is not a function
at e.apiCall (cmp2.js:1)
at new e (cmp2.js:1)
at Module.<anonymous> (cmp2.js:1)
at n (cmp2.js:1)
at Object.<anonymous> (cmp2.js:1)
at n (cmp2.js:1)
at cmp2.js:1
at cmp2.js:1
The second is a “Failed to load resource: the server responded with a status of 403 ()” error for the the following:
https://quantcast.mgr.consensu.org/choice/1mk94hmLDvjYg/www.boroguide.co.uk/.well-known/noniab-vendorlist.json?timestamp=1610656531509
I’ve searched through the forums and the Quantcast Help Centre to find out what I’ve done wrong – but none of the suggestions have so far resolved the issue. What am I missing?
]]>After implementing Quantcast Choice, a bug in adsense 2.1a appeared. I managed to block the ads before giving consent with Adinserter – and its working very well. Unfortunately, earnings dropped terribly after the implementation of your tool. It seems to me that something is still wrong, even if everything seems fine…
And maybe quantcast javascript errors are the problem? I would like a hint as to what could be causing them. Below the error code:
VM154 cmp2.js:2 Uncaught TypeError: n is not a function
at e.apiCall (VM154 cmp2.js:2)
at new e (VM154 cmp2.js:2)
at Module.<anonymous> (VM154 cmp2.js:2)
at n (VM154 cmp2.js:2)
at Object.<anonymous> (VM154 cmp2.js:2)
at n (VM154 cmp2.js:2)
at VM154 cmp2.js:2
at VM154 cmp2.js:2
e.apiCall @ VM154 cmp2.js:2
e @ cmp2.js:2
(anonymous) @ cmp2.js:2
n @ cmp2.js:2
(anonymous) @ cmp2.js:2
n @ cmp2.js:2
(anonymous) @ cmp2.js:2
(anonymous) @ cmp2.js:2
37ed0.js?70b48:2 GET https://quantcast.mgr.consensu.org/choice/As-we4806CGJn/www.mysite.com/.well-known/noniab-vendorlist.json?timestamp=1602958888488 403
Failed to load https://quantcast.mgr.consensu.org/choice/As-we4806CGJn/www.mysite.com/.well-known/noniab-vendorlist.json?timestamp=1602959601561:1 resource: the server responded with a status of 403 ()
Any ideas?
]]>Is there a way to make the pop-up on mobile a bit smaller? Of course, without switching to the small format for desktop. Right now, on iPhone 11, the entire screen is filled by the layover.
]]>There is a UI bug in my opinion with the parent group toggle:
“Precise geolocation and information about device characteristics”
If this is turned off and saved by a user, when they reopen the layer it is on again. Yes the child settings are all set to off however this is a confusing and misleading and already resulted in users contacting us thinking it’s a major bug.
Turning it off and saving:
https://snipboard.io/6pAOrM.jpg
After reopening the layer:
https://snipboard.io/4W0LEq.jpg
Could this be fixed in the next release?
A followup question to this – If the “Use precise geolocation data” checkbox is not used in the sites “Special features” section why does it even appear in the resulting consent layer if it’s not even required by the publisher?? (same goes for all the purpose settings actually):
https://snipboard.io/vO0Urx.jpg