• 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 - 1 through 15 (of 327 total)
  • @rbaronqc @spacetime :
    Reg 2.1a error:
    Adinserter for EU / UK setting in QC : I am getting the consent and ads put in adinserter are getting loaded only after the consent is agreed but only after refreshing the page.Also other ads(for example the top header bannerad to the right of logo) which are in wp widget are loaded before the consent.
    Adinserter for everyone setting in QC : Ads which are inserted through adinseter plugin are not loading at all since consent form will not be shown to other than EU/UK users.This is a major issue impacting revenue.Please fix.

    You can check the screenshot here and test the above in my website : https://www.sharmispassions.com
    Consent form screenshot

    Reg 1.1 error:

    I just saw the error report and even after adding the parameters as suggested in adinserter(euconsent-v2[vendor][consents][755]=1) even 1.1 error is still not reduced.So should I append euconsent-v2[purpose][consents][1]=1 to the existing parameter or delete and add it.

    #1

    This is normal as the cookie check is done immediately after the page is loaded.
    Ad Inserter pro supports also Manual loading which can be used to insert ad codes immediatley after the consent is given (TCF API used by the Choice supports event listeners):
    https://adinserter.pro/faq/gdpr-compliance-cookies-consent#manual-loading

    Ad Inserter inserts blocks (ads) according to the settings. So if you check cookie to see if google ads are enabled and they are not, then the code will not be inserted.
    Maybe plugin authors can clarify how to solve such cases.
    Is the cookie euconsent-v2 generated only for EU visitors?

    #2

    Not related to Ad Inserter.

    Plugin Contributor Ryan

    (@rbaronqc)

    @vsharmilee I am still seeing the old TCFv1 cmp showing up on sharmispassions. If you are using the choice plugin can you make sure you have it set for TCFv2 with your UTID added and TCFv2 enabled. https://vimeo.com/manage/445983282/general. If you are adding the Choice Tag with Google Tag Manager that also works, but just delete the plugin so we can eliminate that as a possible source of the TCF v1 CMP. But my recommendation is to add Choice with the plugin so it can be added to the page as early as possible.

    Ryan @rbaronqc Hello, despite I configured it in the right way, it is not working. I have the latest version on quantcast and TCF V2.0 configurated correctly.

    Also have the good check with Ad Inserter, so should I need to wait then for a solution? because when I click on agree nothing changes, I think that it’s up to you

    Thank you so much for clearifying our doubts.

    Please check my site https://www.musicmundial.com/en/ and tell me if you see changes because I noticed nothing.

    • This reply was modified 4 years, 3 months ago by sneesel.

    @rbaronqc : Just now noticed, one of my website ad provider had their own CMP which might have triggered TCF v1 user consent popup.We have now opted out their CMP and selected the option for using our own CMP(Quantcast).Please check and let us know at the earliest if TCF v1 is still loading.

    We have now deactivated Quantcast for testing purposes – Kindly check for current EU user page that is getting loaded and let us know.If there are no user consent loaded for EU users, then we can activate Quantcast.

    Also we are not using GTM.

    • This reply was modified 4 years, 3 months ago by vsharmilee.
    Plugin Contributor Ryan

    (@rbaronqc)

    @vsharmilee I think that got rid of the TCFv1 CMP. I am no longer seeing it, now let’s activate the Quantcast Choice TCFv2 plugin/cmp.

    @rbaronqc : Thank you for checking!
    We have configured Quantcast Choice as per the instruction given.
    And we are getting the same behaviour like what @ibiza69 says.The ads are not shown at all…Please update us on the solution.

    Plugin Contributor Ryan

    (@rbaronqc)

    @sneesel you are correct that when I click agree no ads appear, but I am seeing ads on all subsequent page views (so that is good). I believe there is either an Ad Inserter config setting that will load on the first close or that @spacetime is working on an update for that as we speak.

    The latest development version of Ad Inserter adds support for multiple checks for cookie list items (&&) and supports true and false constants (current version requires to use 1 and 0):
    https://downloads.www.ads-software.com/plugin/ad-inserter.zip

    The check to use for Google ads is now:

    euconsent-v2[vendor][consents][755]=true && euconsent-v2[purpose][consents][1]=true, euconsent-v2[gdprApplies]=false

    euconsent-v2[vendor][consents][755]=true means consent for Google Advertising Products

    euconsent-v2[purpose][consents][1]=true means consent for “Purpose 1 – Store and/or access information on a device”

    euconsent-v2[gdprApplies]=false whitelists the block for users where GDPR does not apply.

    When asking for support for Ad Inserter please enable Remote debugging (tab ? / tab Debugging) and follow the rules:
    https://www.ads-software.com/support/topic/ad-inserter-support-before-you-ask-for-help/

    Plugin Contributor Ryan

    (@rbaronqc)

    Awesome

    • This reply was modified 4 years, 3 months ago by Ryan.

    @spacetime : Thank you!
    Will update the latest development version of Ad Inserter along with the new updated euconsent (&&) code and let you know the proceedings.Will enable remote debugging if we still find issues.

    @spacetime : Have implemented the updated euconsent(&&) code in the adinserter plugin 2.6.11 and following are the observations from India:
    1.The 2 ads that have new && code does not load before user consent.
    2.But even after user is agreeing the consent, those 2 ads are not loaded.
    I tried refreshing the page even then it is not loaded.

    NOTE : The other ads that may load before and after consent are not part of adinserter plugin hence we can skip those ads for testing now.

    Checklist for remote debugging:
    1.Enable Remote debugging (tab ? / tab Debugging). – Yes done
    2.You may need to disable caching, otherwise debugging functions will not work – Yes done
    3.Clearly describe the problem. Describe what does not work as expected. – described as above
    4.Describe the settings and code blocks used. – euconsent && code added in 1,2 code blocks alone.
    5.Post web addresses (links) of the pages where the code from the settings above is not inserted properly – https://www.sharmispassions.com

    Kindly check and do the needful.

    1. You have javascript errors on the page in script blogherads.js:2:
    Boomerang: A slot with ID skm-ad-medrec-1 already exists.
    Error: A slot with ID skm-ad-medrec-1 already exists.
    https://ads.blogherads.com/static/blogherads.js

    2. On the posts you have AdSense ads for which the code is not inserted via Ad Inserter (sidebar, header)

    3. You are not using the latest version as instructed:
    https://downloads.www.ads-software.com/plugin/ad-inserter.zip

    After you install the latest version I can check again.

    @spacetime
    My website is brzikolaci.com

    I have the exact same problem as vsharmilee, implemented ads with latest 2.6.11, using Quantcast, and ads don’t even show up for people outside EU (I am outside EU). Using TunnelBear, I can see they are not showing for EU users either, after accepting everything in Quantcast banner.

    Using client-side insert, euconsent-v2[vendor][consents][755]=true && euconsent-v2[purpose][consents][1]=true, euconsent-v2[gdprApplies]=false
    remote debugging enabled, cache disabled,

    Plugin Contributor Ryan

    (@rbaronqc)

    @cvrle77 a couple of things.

    1. On first visit, after agreeing, I did not see ads, however on all page views after that I do see ads appearing.

    2. It sounds like you might only want to show the CMP for users in the European Economic Area (EAA) and UK, you can do this by going to https://quantcast.com/protect/sites, clicking the pencil icon for your domain, and setting the CMP to show only for EAA and UK visitors. only-show-cmp-in-eaa-uk

    If you do the above, Quantcast will set the tcData.gdprApplies to false for all those visiting outside the EAA & UK, and it is my understanding that if you install the latest development version of the Ad Inserter plugin and set Ad Inserter configuration up as mentioned here https://www.ads-software.com/support/topic/choice-ad-inserter-setup-support/#post-13294432 Ad Inserter will now read the `tcData.gdprApplies’ value and show ads as normal when GDPR does not apply.

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