• 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 - 91 through 105 (of 327 total)
  • If I turn GTM preview mode, there’s no error that I wrote about in previous post, on any of my websites. (??)

    Hi @spacetime @rbaronqc :
    I just saw the updated error report now : Finding the error count decreasing but the errors have been detected on 24th August also which is after configuring the updates from Adinserter and QC.So I am confused if the problem is recurring.Kindly advise.

    Screenshot of todays error report:
    https://drive.google.com/file/d/1yO6OFjRJYjEbXsH6_8Pb4MbIPNKBq_5y/view?usp=sharing

    Hi @spacetime and @rbaronqc, today I could check well and I’m facing exact same problem as @vsharmilee, errors decreased a bit, but all errors are still there at Adsense, after implementing Adinserter Pro and Quantcast. I was working hand to hand the day before yesterday with Ad Inserter plugin developer to have everything correct (ads do not load, until Quantcast choice is accepted), so maybe the problem comes thru Quantcast? What you think both? Thanks in advance!

    I would suggest to ask some AdSense expert. It is very hard to diagnose why those messages appear and where the problem is.

    If I understand correctly a publisher from EU needs to ask for the consent ALL visitors, while publishers outside EU only those in EU.
    This is a setting in the Choice plugin.

    @spacetime, thanks! We tryed hiring an Adsense expert a few days ago as I wrote in another post, but finally had to return the money (cancel de order), because didn’t know how to solve it by depending on Quantcast and Adinserter. The situation is complex at all levels…

    I’m not sure how can we control or solve this type of errors by our side, as seems something that Quantcast has to analyze and see why it’s happening, maybe?, not sure:

    – ERROR: 1.1

    – DESCRIPTION:
    Google, as a vendor, is not allowed under consent or legitimate interest.

    – SUGGESTED ACTION TO TAKE:
    Confirm whether the user intentionally rejected Google as a vendor, CMP implementation errors have occurred, or there are publisher restrictions.

    ++++++++++++++++++++++++++++++++++++++++++++++

    – ERROR: 2.1a

    – DESCRIPTION:
    Tag or SDK isn’t receiving a TC string due to CMP status being stub, loading, or error.

    – SUGGESTED ACTION TO TAKE:
    If you’re manually invoking the function to request ads, make sure the response to getTCData TCData.eventStatus = ‘tcloaded’ OR ‘cmpuishown’ + ‘useractioncomplete’. These indicate the CMP is ready to provide the user with a choice regarding consent.

    If you’re not manually invoking the function to request ads, then work with your CMP to ensure they implement support for getTCData and return TCData.eventStatus = ‘tcloaded’ OR ‘cmpuishown’ + ‘useractioncomplete’ to indicate the user consent is ready for use through the API.

    +++++++++++++++++++++++++++++++++++++++++++++

    I Found too what that Unknown website list means:

    Unknown domain (Desconocido):

    DESCRIPTION:
    Ad requests detected from a domain that is not registered in the account.

    COMMENT:
    A small percentage of such requests is normal, as some users can access the site’s content from caches of 3rd party web services.

    MONETIZATION STATUS:
    Often, error 1.1 is stated for Unknown domain events. In this case, the ad requests are not filled.

    @rbaronqc @spacetime : The error count has started increasing in todays report and last detected date shows as 25th August so the code is missing something I guess.Kindly check and advise.

    Hello everyone and @rbaronqc.

    I am going nuts trying to implement choice + ad inserter, as I am getting error 2.1a in AdSense. I have installed choice on my website https://www.starswelt.com, but I got a problem with targeting cookie parameters in ad inserter. Whenever I insert the following value “euconsent-v2[vendor][consents][755]=true && euconsent-v2[purpose][consents][1]=true, euconsent-v2[gdprApplies]=false” my ad wont load and in debugging i get the error waITING FOR tcData. I see that cookie euconsent-v2 is stored in https://www.starswelt.com instead of .starswelt.com. Is there maybe something else I should include in my code to target a consent cookie? Even if I only put euconsent-v2 in URL parameters I also get the same waiting for TcData error.

    I have bought adinserter pro hoping that this will maybe fix this error, but no luck so far. My revenue is plummeting and I am kinda in despair to get a fix ASAP.

    Thanks in advance to anyone who might help.

    • This reply was modified 4 years, 2 months ago by fanstebg.
    • This reply was modified 4 years, 2 months ago by fanstebg.
    Plugin Contributor Ryan

    (@rbaronqc)

    @vsharmilee @spacetime when loading the page sharmispassions.com I still see ads in the background, when I have not yet given consent.
    visible-ad-too-early

    Also when I check the code on the page I see google scripts on the page before I have given consent. I’m not sure if there is more than 1 plugin at play adding scripts to the page but I think that this is the issue. It is my understanding that these scripts cannot be added to the page with out consent. If I look at the code without having yet given consent I see a tag for “https://pagead2.googlesyndication.com/pagead/…” and some other google ad related tags.

    visible-tags-too-early

    • This reply was modified 4 years, 2 months ago by Ryan. Reason: Linking to higher quality image to see details

    @rbaronqc @vsharmilee

    Ad Inserter (Pro) inserts the codes as configured.
    So if you have configured blocks to insert the code when euconsent-v2 conditions are present, then the blocks (the ad codes) are inserted ONLY when the consent is given and euconsent-v2 coditions are present.
    You can always check thr source code and use debugging functions to label blocks.

    Very likely you are inserting those scripts (found in the source code) outside of Ad Inserter (other plugins, theme settings, hardcoded in theme files, etc).

    @spacetime @rbaronqc All the ads that I have placed manually is inside adinserter plugin only but the ad in the screenshot you had given and few other ads in sidebar I see..Should be from google adsense autoads which is outside of adinserter.Autoads are ads placed by google when we enable autoads tab in adsense settings.Kindly advise how do we take care of consent for autoads?

    @fanstebg

    The debugging message WAITING FOR tcData shown for each block configured for euconsent-v2 cookie is not an error.

    It only means that Ad Inserter is waiting for the TCF API data (used by Quantcast Choice) to return consent data.
    This usually happens before the consent is given.

    Remote debugging on https://www.starswelt.com doesn’t seem to be enabled so I can’t check.

    @spacetime @rbaronqc :
    Hi,
    I have a query so wanted to confirm.
    Do you have any idea how to bring autoads into adinserter? or
    Can the google ads header script be included in adinserter itself? so that all the ads that come from google will be through adinserter.

    @spacetime @rbaronqc

    I managed to successfully implement ads to wait for consent on my second website https://www.planetecelebre.com/top-12-des-plus-belles-joueuses-de-football-au-monde/ , but now my ad sizes are completely broken and they go above layout, while some ads are a smaller size than normal.

    @vsharmilee

    For ANY (javascript) code that needs to be inserted only after the consent is given:

    Put the code in a block, select No wrapping as alignmet, Footer (for example) as insertion position and define cookie conditions.
    Then the code will be inserted only when the consent is given.

    @fanstebg

    Usually this happens when the responsive AdSense code does not identify available width properly – maybe because of the layopt of your theme.
    Try to use fixed ad sizes.

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