Quantcast choice + Advanced Ads still under 2.1a error

Hi versus,

thanks for reaching out.

I checked your home page and can confirm that there is no call to AdSense.

On a subpage like this, I can find a call to a URL like https://googleads.g.doubleclick.net/pagead/id when looking at the Network tab in the developer tools. This looks like an ads URL, but there is no AdSense code so it is definitely not coming from Advanced Ads.

I have seen your post in the Quantcast forum as well and hope they have an answer for this. As for the requirement to not load AdSense codes without consent, I can confirm that this works as expected.

Out of curiosity: was there no change at all to the number of TCF issues in the last 7 days?

Thanks,
Thomas

Hi @webzunft No, no change from the las 7 days, https://www.criticmedia.ro,2.1a,566,27/09/2020, only the update date changes.

Yes, I post the same in the Quantcast forum, no reply received yet! Maybe the don’t know either what to reply!

I have no other Ads plugins installed right now and which I had I reset it, and no other adsense codes inserted, only through Advanced Ads, maybe shortcodes inserted in Ads Options theme could interferes somehow!?

I dont know what and how screwed up the TCF 2.0 compliance.

Could be some transients remained in the database interferes? I suposed not! Right?

Regards
Dani

Hi Dani,

on the pages I checked, there is definitely no call to AdSense before consent is given. I am not just looking into the code, but also into the Network tab in the browser console, which lists all scripts. AdSense would definitely appear there if it was called.

I also just double-checked with the instructions Quantcast is giving and our implementation matches it as well. Since not only our users but also users of other TCF integrations complain about this issue, I guess that it comes from somewhere else.

Thomas

Hi Thomas!

So it’s somehow a possible Quantcast issue here which interfres with consent Ads?

If i migrate to the other CMP with TCF 2.0 implementation, Onetrust…or else, might have solve what I have face here? Or is somewhere between Advanced Ads and CMP, could be a plugin or else?

Regards
Dani

Hi Dani,

our TCF integration works with any CMP that follows the TCF API. Unfortunately, I cannot look into the blackbox that is the communication between CMP and Google. I have seen the same issue happening to users of other CMPs and don’t want to point fingers at someone specific without being absolutely sure.

If you or anyone else finds someone competent to look into this then they will get my full support.

Thomas

Has anyone here try Advanced Ads with other CMP than Quantcast without 2.1a error?

Thanks!

Hi @webzunft

Today, my website escaladet, not only that I’m not escaped from 2.1.a, but I have 5.1 also, so I have both now!

This is Out-of-Band consent I supose! I didn’t have that before!

https://www.criticmedia.ro,2.1a,349,29.09.2020
https://www.criticmedia.ro,5.1,197,30.09.2020

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

Hi @sirvss,

I checked this article from Quantcast. It looks like 5.1 is related to CMPs and Quantcast itself, though they clearly state that they don’t even have that option.

Advanced Ads does not manipulate the TCF string so it is not related to the plugin.

I still checked your site and the TCF string on it. The outOfBand parameter is empty.

Quantcast also complains about your site not using HTTPS consistently. Maybe that breaks the communication with them somehow. Is it possible that you told them that your site uses HTTP?

I hope this helps.

Thomas

Hi @webzunft !

Sorry but I didn’t see where they complains about my HTTPS protocol, I checed with my host provider and they assure me that my HTTPS provide by their cPanel are implemented as it should be. Also I tried HTTP only for few days and I didn’t get 2.1a error free, now I get another one, even bigger!

Thanks Thomas!

Sorry, the issue is not from Quantcast.

This is what appears in the browser console:

> Uncaught (in promise) p: OneSignal: This web push config can only be used on https://www.criticmedia.ro. Your current origin is https://www.criticmedia.ro.
at Function.checkRestrictedOrigin (https://cdn.onesignal.com/sdks/OneSignalPageSDKES6.js?v=151104:1:211456)

and

> Mixed Content: The page at ‘https://www.criticmedia.ro/’ was loaded over HTTPS, but requested an insecure favicon ‘https://www.criticmedia.ro/wp-content/uploads/2020/02/favicon-1.png’. This request has been blocked; the content must be served over HTTPS.

I cannot say anything about the other issue. The fact that we didn’t make any changes before they appeared in your reports confirms that the source is somewhere else.

Maybe the Quantcast Choices release notes include a hint you can you.

Thomas

Hi @webzunft!

Thanks again because enlight me, I fixed all that errorsm still I left with another three one, one I don’t know where is coming frome, but two is definetly from Quantcast Choise plugin!

DevTools failed to load SourceMap: Could not load content for https://www.criticmedia.ro/wp-content/plugins/quantcast-choice/public/css/style.min.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load SourceMap: Could not load content for https://www.criticmedia.ro/wp-content/plugins/quantcast-choice/public/js/script.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

Thosee, I don’t know how to fix or even it can be fix, but beeing css and js interogation, if affect with something 2.1a and 5.1 errors!

Regards!
Dani

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