• Resolved av83000

    (@av83000)


    Hello,

    I use Teads to monetize my site.

    This board offers to view the statistics of our GDPR consent.

    But since the passage of the Quantcast code into TFC 2.0 on August 15, the consent statistics given by Teads about my account have totally dropped.

    I have about 65% response “unknow”

    For exemple, today is : 68,18 % no response: we did not get a response to a __cmp request after a specified timeout

    I don’t understand why… my stats on Quantcast are good with 75% accept.

    My website is : blog-rct.com

    Can you help me ?

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Contributor Ryan

    (@rbaronqc)

    @av83000 im seeing a js error causing the issue, I found an internal ticket with for this issue, the product team is looking into this issue already. I added your url to the list if sites seeing this issue. I will update you when I see updates there.

    Thread Starter av83000

    (@av83000)

    Okay, thank you for your answer

    I guess this is a compatibility issue with another wordpress plugin that created this error?

    Since this transition to TFC 2,0, my monetization is terribly impacted…

    Thank you in advance

    Thread Starter av83000

    (@av83000)

    Hello,

    When I put the version 8 of Quantcast instead of the 9, it seems to work properly.

    What is the difference between version 8 and version 9? Are both versions TCF 2.0?

    Thank you in advance for your answer

    Plugin Contributor Ryan

    (@rbaronqc)

    @av83000 I am still waiting to hear back from the product team on our side about the “Uncaught TypeError: Cannot create property ‘addtlConsent’ on boolean ‘false'” you are seeing. I will update as soon as I have more information.

    Diff between 8 and 9
    You can the Choice Changelog here. https://help.quantcast.com/hc/en-us/articles/360047357574-Quantcast-Choice-Code-Release-Notes-TCF-v2-0-

    Yes, version 8 is TCFv2!, if switching to from v8 to v9 fixes the issue I would suggest doing that short term until I get more info from the product team here. You will def not want to stay on 8 long term (and instead stay on the latest version), but short term, if it works I would switch to 8 and then check back here or updates on the long term fix.

    Thread Starter av83000

    (@av83000)

    ok thank you very much! I switch to Version 8 while waiting for your news.

    Thank you again!

    @rbaronqc I tried to upgrade to version 8, but the problem persists. Do you have updates?

    Plugin Contributor Ryan

    (@rbaronqc)

    @soter80 the product team is actively working on this specific issue. I am monitoring the internal ticket and will update with any significant news when it becomes available.

    Plugin Contributor Ryan

    (@rbaronqc)

    @soter80 product team just pushed out v10 of Choice with a fix that I believe will solve your issue can you confirm?

    Plugin Contributor Ryan

    (@rbaronqc)

    @av83000 please update to Choice v10 and let me know if this solves your issue.

    Thread Starter av83000

    (@av83000)

    Hi Ryan,

    version 10 allows the banner to display correctly. No problem on mobile.

    On the other hand, there is a problem on desktop.

    When I click on “I agree”, the blindfold does not close.

    Here is the error message in the chrome console:

    cmp2.js:2 Uncaught TypeError: Cannot read property ‘postMessage’ of null
    at t.callback ((index):108)
    at t.e.invokeCallback (cmp2.js:2)
    at t.e (cmp2.js:2)
    at new t (cmp2.js:2)
    at cmp2.js:2
    at Map.forEach (<anonymous>)
    at e.exec (cmp2.js:2)
    at e.update (cmp2.js:2)
    at Object.dispatch (cmp2.js:2)
    at e.value (cmp2.js:2)

    Thread Starter av83000

    (@av83000)

    do you have a solution for me ?

    Thanks a lot !

    Plugin Contributor Ryan

    (@rbaronqc)

    @av83000 are you still seeing the unknown response issue or did the latest Quantcast Choice updates resolve the issue for you?

    Plugin Contributor Ryan

    (@rbaronqc)

    Closing the issue due to inactivity by the original author.

    If you are having a similar issue please check the support forums for an existing answer before opening up a new support request.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘65% unknown response in Quantcast ! Why ?’ is closed to new replies.