IAB TCF 3.2 Error

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support schmidt25

    (@schmidt25)

    Hi fynight,

    Thanks for reaching out.

    Based on the page behind your link, there is nothing else to do and Quantcast will reprompt consumers if the consent string creation date reaches 13 months of age.

    Best regards,
    Joachim

    Thread Starter fynight

    (@fynight)

    so when google brings up that error there is nothing for me to worry about. p.s now using Quantcast as per say, using network N core consent added site to the original post so you can see it

    • This reply was modified 4 years, 1 month ago by fynight.
    • This reply was modified 4 years, 1 month ago by fynight.
    Plugin Support schmidt25

    (@schmidt25)

    Hi fynight,

    Thanks for adding the link. No AdSense scripts are loaded into the site before I give the consent. Afterward, the ads appear. Looks fine.

    Best regards,
    Joachim

    Thread Starter fynight

    (@fynight)

    thats what i know as well, just google popped up 84 IAB TCF 3.2 Errors today, last found 9th October, but like I can find a way to fix this.

    Plugin Support schmidt25

    (@schmidt25)

    Hi fynight,

    Thanks for the explanation. But this issue looks like a problem between AdSense and your CMP (Quantcast). I recommend reaching out to the Quantcast support in case you don’t feel comfortable with this warning in your AdSense account (what I can absolutely understand).

    Advanced Ads import the notification only from your AdSense account.

    Here, you can find the official AdSense information about the 3.2 error.

    Best regards,
    Joachim

    Thread Starter fynight

    (@fynight)

    Not going to do that, this is the first time the 3.2 error has arrived, ever, should disappear I hope.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘IAB TCF 3.2 Error’ is closed to new replies.