• Plugin Contributor Ryan

    (@rbaronqc)


    Choice + Ad Inserter Plugin

    Blocking ads until consent a user has given consent. See the “How to show ads based on visitors’ consent?” section in their help documentation here. Showing you how to whitelist consent cookies such as the Google Advertising Products Cookie (euconsent-v2[vendor][consents][755]=1) and you also have to Make sure you have Dynamic blocks set to client-side insert – TCF v2.0 based cookie needs to be checked client-side (in the browser).

    * If you are still seeing 1.1 errors, you may also need to whitelist euconsent-v2[purpose][consents][1]=1 to check for Purpose one consent as well.

    Note: Ad Inserter has added some specific guidance related to Quantcast Choice on their help page, but any instructions pertaining to TCF v2.0 on should also be relevant for Quantcast Choice as we are a TCF v2.0 compliant CMP.

    Please make sure you have attempted to follow the blocking instructions provided by Ad Inserter (see above) before reporting Google 2.1a and 1.1 errors here.

Viewing 15 replies - 181 through 195 (of 327 total)
  • @fanstebg

    Nice that you solved this problem! Did you use this code?
    https://stackoverflow.com/questions/63440572/how-to-display-or-block-personalized-adsense-ads-based-on-consent-for-iab-tcf-v2

    • This reply was modified 4 years, 6 months ago by boothby.

    @boothby

    Yes, the second one.

    Be sure to remove all URL parameters from ad inserter blooks, set manual loading to the disabled. Also in the general tab, set dynamic blocks back to the server-side and that should be it.

    Let me know if you tried this and if it worked for you, would be nice if someone else could confirm it.

    Hi @fanstebg!

    Can you give us instructions how you did it, please?

    I read what is stated in the url posted by @boothby, but I don’t know what to do with the code or where to insert it.

    I’m using Quantcast Choice and AdInserter configured as stated in this discussion and I keep getting 2.1a errors.

    Thank you!

    @reamca

    use the second code and do it like in the image below:

    View post on imgur.com

    I have only tried it myself for a short time and it seems to work. But I did not test it properly.

    • This reply was modified 4 years, 6 months ago by boothby.

    @vsharmilee & @spacetime, in todays adsense report ONE of the sites increased its errors…, instead of descreasing as all past days.

    No changes where made to any of our sites since we made them with the help of Ad Inserter developer.

    So, can’t underestand or know why 2.1a errors increased today ?? As Adsense doesn’t explain anything.

    Just for letting you know, other of our sites still decreasing number of errors.

    @rbaronqc @spacetime : Since I had a doubt, I removed shemedia overlay ad from my website yesterday just to check and was quite surprised to see the error report today with last error detected date as 27th august.So that means the overlay ad from shemedia which is called through headerscript code placed inside adinserter did not work as expected and is the cause for repeated 2.1 error.Can you provide an updated code which will take care of this situation?

    @ibiza69 : Thanks for the update.

    Not sure how shemedia ad could have impact on AdSense reports.
    And if you removed the shemedia ad yesterday and it was causing AdSesne errors, there is no way to have last AdSense error detected on 27th August. To me this only confirms is has no impact on AdSense.

    It seems it is only some correlation which does not imply causation.

    @spacetime : Thank you for the clarificarion.Today I’ve enabled the overlay ad so we can confirm it after seeing tomorrows error report.Will update tomorrow about the error report.

    I did not receive any error messages on September 1st.

    I replaced the CMP on September 2nd to see what happens. I had massive problems with this CMP the previous weeks. In today’s error report I had a number of 467 2.1a errors. Normally the number should be between 40,000 and 50,000 errors.

    Either the reports are faulty or Google has made improvements and can process the signals of the CMPs better.

    If you have implemented everything correctly, wait for the next few days. I think the number of errors will continue to decrease.

    By the way, I did not use the stackoverflow script mentioned above.

    @ibiza69

    Maybe you did get on this site more visitors than the other days, that is probably the reason why the number of errors increases.

    • This reply was modified 4 years, 6 months ago by boothby.
    • This reply was modified 4 years, 6 months ago by boothby.

    @boothby hi, what CMP are you using? Quantcast?

    Hi to all, good morning ??.

    Today I downloaded the Adsense daily report and there was only 1 site “Unknown” with error 1.1 and 40 errors, all others where gone ??.

    Don’t know if is an Andense report error of if problems where solved in all our sites, as yesterday many of them had still a few (decreasing, but a few)…

    Did any of you faced something similar?

    Thanks!

    Good morning people!

    This is really confusing.
    I implemented the method of:
    – Quantcast Chioce + AdInserter plugins with URL parameters for Google Adsense. And it apparently works, as the ads don’t show until the consent banner is accepted.
    But the Google Adsense reports I get are incomprehensibles.
    Yesterday I received an updated report as of September 1 with many errors.
    But the date of today’s report update is August 26.

    I don’t understand anything.

    Google published a new Consent Mode yesterday. It is now up to the individual CMPs to integrate this function. You can read more about here: https://support.cookiebot.com/hc/en-us/articles/360016047000

    Maybe @rbaronqc can tell us if this has already been integrated at Quantcast.

    @sneesel i did use Quantcast and switched to cookiepro just to test it out. Both CMPs have delivered similar results in the last three days. Currently I have very few error messages. I am looking forward to this evening when the new report is ready.

    @fanstebg

    Yes, the second one.

    Be sure to remove all URL parameters from ad inserter blooks, set manual loading to the disabled. Also in the general tab, set dynamic blocks back to the server-side and that should be it.

    Can you give us a screenshot from ad inserter settings? (the bold on blockquote)

    thank you

    @boothby this new Consent Mode is only for those who use google tag manager (gtag.js)?

    I use Google Ad Manager (gpt.js)

Viewing 15 replies - 181 through 195 (of 327 total)
  • The topic ‘Choice + Ad Inserter Setup & Support’ is closed to new replies.