• 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 - 211 through 225 (of 327 total)
  • @vsharmilee, apart of our new today errors that where gone, the 1.1 eror Unknow hasn’t changed for last week too. The errors I reported where from today 2.1a (our websites), the one 1.1 is daily, never went away. Hopefully this informarion helps you ??

    So, it’s increasing for no obvious reasons.

    brzikolaci.com,2.1a,473,9/8/2020

    Tested, and form works from my side, as it should. No ads, no tags before user gives his consent (unless I am missing some underlying code that goes crazy without my knowledge)

    Still having problems using Quantcast and Ad Inserter ?? hope someone can help us!

    Hi @sneesel, we keep on getting errors:

    “Unknown”: ERROR 1.1

    09-09-20——–122—–04-09-2020
    10-09-20——–122—–04-09-2020
    11-09-20——–309—–09-09-2020

    All these websites shown below disappeared from the list on September 4 and the errors returned on September 9:

    Website 1: ERROR 2.1a
    09-09-20——–391—–04-09-2020
    10-09-20——–391—–04-09-2020
    11-09-20——–391—–04-09-2020

    Website 2: ERROR 2.1a
    09-09-20——–186—–04-09-2020
    10-09-20——–186—–04-09-2020
    11-09-20——–186—–04-09-2020

    Website 3: ERROR 2.1a
    09-09-20——–169—–03-09-2020
    10-09-20——–169—–03-09-2020
    11-09-20——–169—–03-09-2020

    Website 4: ERROR 2.1a
    09-09-20——–313—–03-09-2020
    10-09-20——–313—–03-09-2020
    11-09-20——–152—–09-09-2020

    Website 4: ERROR 2.1a
    09-09-20——–103—–03-09-2020
    10-09-20——–103—–03-09-2020
    11-09-20——–103—–03-09-2020

    Just don’t know what could be happening, as Adsense doesn’t provide any information for getting with the possible solution.

    @spacetime @rbaronqc : Yay! Finally no errors on my adsense dashboard! Huge relief after almost a month long struggle.Thank you @spacetime @rbaronqc for your timely support and patience.

    @ibiza69 : Finally no errors on my adsense dashboard since yesterday evening.I did not do anything new…it was the same steps as suggested by the authors and it took so long to get updated I guess.

    Plugin Contributor Ryan

    (@rbaronqc)

    @vsharmilee that is awesome news!

    @vsharmilee great ??

    @vsharmilee GREAT!!! You worked hard to achieve it ????!! Now, have a really nice weekend ??!!!

    @vsharmilee can you share with us your settings?

    @ibiza69 : Thank you!

    @aldon : Sure..This is what I did:
    1.Create a account with quantcast choice – Followed instructions in the page
    2.Add your website under privacy
    3.Privacy settings screenshot here :
    Privacy setting
    Privacy setting continued
    4.TCF V2 settings screenshot
    5.Bring all the ad codes inside adinserter plugin.In adinserter settings > General > set dynamic blocks to client side insert
    6.Add this in url parameters:
    euconsent-v2[vendor][consents][755]=true && euconsent-v2[purpose][consents][1]=true, euconsent-v2[gdprApplies]=false
    change 755 according to your ad vendor if you are using other ads.755 is for google.

    Kindly check instructions by both plugin authors and verify it.
    It may take time for the error warning on the adsense dashboard to disappear(for me it took around 10 days).The last detected date should be fixed at a particular date without changing daily,then that is a notification the error warning will vanish in a while.Hope this helps!

    • This reply was modified 4 years, 2 months ago by vsharmilee.

    @vsharmilee : Thanks for your above explanation. I implemented the same with the help of Ad Inserter Pro technical support. Something like 2 weeks back. But I still got Error 2.1a.

    I am not a developer and have a few questions.

    1. If I don’t implement TCF v2.0 completely, will my Adsense Ads stop displaying to everyone or only EEA/UK users.
    2. Will this reduce my Adsense earnings. I find that implementing TCF 2.0 using the above method has reduced the earnings. So I’m just using the traditional GDPR message as of now.
    3. Will my Adsense account be banned, if I don’t implement TCF v2.0

    Just for information sake,

    SITE 1- not implementing TCF , but using GDPR message.

    Domain Error Error count Last detected date
    site 1 2.1a 22 9/5/2020

    SITE 2 – implemented TCF as mentioned above, using only Adsense Ads
    No error message.

    Does this mean the combination of Quantcast Choice + Ad Inserter Pro (with correct settings) works for Adsense.

    Please share some light from your experience

    • This reply was modified 4 years, 2 months ago by shreen2008.

    Totally agree with @shreen2008 . The Quantcast Ad Inserter pro method is functional, but absolutely impacting on earnings. The CTR dropped consistently. It is currently not applicable as is. I hope adsense takes action.

    Hi to all, I had an small question. Do you know if it’s possible to add google analytics to the header code at website or should be placed other way for not getting errors at TCF 2.0? Thanks!

    Sure.

    You need to use one block and configure it to be inserted only when the consent is given.

    Set Automatic insertion to Header (code in the <head></head> section) or Footer (code before the </body> tag).

    Normally, position for automatic insertion Header does not exist and needs to be created. Go to tab ? / tab Hooks and create and enable hook with name Header and action wp_head. After you save settings you’ll get Header position for automatic insertion for each code block.

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