Quantcast choice + Universal tag + TCF 2.0

  • Hi there!

    If Universal Tag ID (UTID) was added in the QC Choice plugin, Universal Tag is needed to be added in the <head> too in order to became TCF 2.0 compliant?

    Thanks!

    Regards

    • This topic was modified 4 years, 2 months ago by versus.
    • This topic was modified 4 years, 2 months ago by versus.

    The page I need help with: [log in to see the link]

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

    (@rbaronqc)

    @sirvss, If you are using the QC Choice plugin (and added your UTID) the plugin will automatically add the Quantcast Universal Tag to the <head> of your website.

    The plugin essentially does 3 things:
    – Adds the Quantcast Universal Tag to the <head> of the site
    – (optional) Automatically pushes consent signals to the data layer (when the option is enabled on the plugin admin page). This option is for users who need consent signals accessible for 3rd party tools like Google Tag Manager. This option can be enabled/disabled on the plugin admin page.
    – (optional) Automatically adds CCPA Do not sell my data message and link to an empty container added to the footer of the website. This option can be enabled/disabled on the plugin admin page. In order for this feature to work you also have to have CCPA enabled on your tag from the quantcast.com portal.

    Thread Starter versus

    (@sirvss)

    Ok, @rbaronqc good to know, I deleted my universal tag then!

    Thanks for your detailed clarification!

    I hope that my critimedia.ro will be TCF 2.0 compliant, because the 30 days grace period expired today, any I still have 2.1a error

    Plugin Contributor Ryan

    (@rbaronqc)

    @sirvss I was previously seeing this error on the site:

    Uncaught TypeError: n is not a function
    at e.apiCall (VM373 cmp2.js:2)
    at new e (VM373 cmp2.js:2)
    at Module.<anonymous> (VM373 cmp2.js:2)
    at n (VM373 cmp2.js:2)
    at Object.<anonymous> (VM373 cmp2.js:2)
    at n (VM373 cmp2.js:2)
    at VM373 cmp2.js:2
    at VM373 cmp2.js:2

    But now, after your removal of the 2nd tag that js error is no longer present.

    Thread Starter versus

    (@sirvss)

    Ok, thank you!

    So basically…my website has no reason to keep 2.1a error anymore, right?!

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

    (@rbaronqc)

    @sirvss that depends upon when Google Advertising Tags are added to the page/attempt to read the consent signals. This is simplified, but Quantcast Choice will ask for, store, and make accessible user consent choices. It is up to the site owner (ad plugin) wait for, read and respect those consent choices. For example, if a user visits the website and a Google Advertising Tags are added in the background before the user selects their consent, that will result in a 2.1a error. When you add a Google Advertising Tag to your site, that tag/script will attempt to read the TCF v2 consent signals, if those signals are not yet set by the user and Google attempts to read them it will result in a 2.1a error. We put out some additional information here https://www.quantcast.com/blog/google-error-code-2-1a-protecting-your-ad-revenue/ to help with 2.1a errors

    Thread Starter versus

    (@sirvss)

    Huh, it’s really exhausting, so many permutation in order to make this work, and I try this from the TCF 2.0 day 1, that was in 15 August.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Quantcast choice + Universal tag + TCF 2.0’ is closed to new replies.