PubConsent
Web Standard Integration

6min
Once you've opened and configured your CMP, in the integration tab, you'll find instructions to add PubConsent CMP to your site in just a few simple clicks.
Tab integrazione configuratore PubCosent
﻿
For integration, make sure to follow the instructions and do not modify the integration code provided in the panel, as the integration code ensures cross-browser support of the CMP and performance improvements specific to the user's browser.
Be careful to avoid duplicates of the CMP script tag.
To offer users a better experience, we recommend placing the CMP script tag inside the  tag and as close to the top as possible.
Follow our Performance tips﻿ to improve integration and the experience of your users.
In addition to the integration code of the JS code, you can configure a callback that is executed when a user gives or changes consent.
An example is provided below:
HTML
...
<head>
    <!-- top head integration code copied from configurator in integration tab -->

	<script>
		var __pubtech_queue_on_consent = __pubtech_queue_on_consent || [];
        __pubtech_queue_on_consent.push(function publisherRead(cmpType, data) => {            
        if (cmpType == 'TCF-V2-GDPR') {
	      console.log("ConsentData", data.consentBundle);
	  
	      console.log("ConsentObject", data.consentBaseApi);
	  
	      console.log("PublisherConsentObject", data.integrations.cookieConsents);
	    }
        });
	</script>
</head>
...
...
<head>
    <!-- top head integration code copied from configurator in integration tab -->

	<script>
		var __pubtech_queue_on_consent = __pubtech_queue_on_consent || [];
        __pubtech_queue_on_consent.push(function publisherRead(cmpType, data) => {            
        if (cmpType == 'TCF-V2-GDPR') {
	      console.log("ConsentData", data.consentBundle);
	  
	      console.log("ConsentObject", data.consentBaseApi);
	  
	      console.log("PublisherConsentObject", data.integrations.cookieConsents);
	    }
        });
	</script>
</head>
...
﻿
Please note that the CCPA version will be available soon.
In the "onConsent" callback shown in the example, there are 3 input parameters:
consentData: An object that always contains the "privacyLaw" field, which can be 'TCF-V2-GDPR' or 'GOOGLE-CONSENT-MODE'. When the version is GDPR, it also contains tcString, acString, and pcString, while when the version is GOOGLE-CONSENT-MODE, it contains things relative to the Google Consent Mode. These strings represent the current state of the user's choices for each privacy law (later the field will be changed to cmpType since it's more appropriate).
consentObject: An object that contains additional information about consent. When the privacy law is GDPR, there is information related to the IAB framework, while when it is GOOGLE-CONSENT-MODE, there is information related to GCM V2.
publisherConsentObject: An object that contains information about the user's choices regarding cookies (information not belonging to the IAB framework). Currently available only when GDPR privacy law applies to the user.
Most publishers use the consentObject to verify the possibility of serving advertisements. Below is an example of a configuration with specific logic to check if certain IAB purposes have been accepted by the user.
JS
__pubtech_queue_on_consent.push(function onConsent(cmpType, data) {
    const tcfData = data.consentBaseApi;
    const publisherConsentObject = data.integrations.cookieConsents;
    if (consentData.privacyLaw == 'TCF-V2-GDPR') {
       let purposeRequired;
       const purposeIdRequired = [1,2,3,4,5,6,7,8,9,10,11];
       purposeIdRequired.forEach(function start(id) {
           purposeRequired = (tcfData.purposeConsents.has(id) === true && purposeRequired !== false) ? true : false;
       })

       if (purposeRequired) {
          console.log('Cookie accepted');
       } else {
          console.log('Cookie refused');
       }

       console.log(publisherConsentObject.featureCookiesChoice); //Return true if is enabled
       console.log(publisherConsentObject.measurementCookiesChoice); //Return true if is enabled
       console.log(publisherConsentObject.userExperienceCookiesChoice); //Return true if is enabled
   }
  });
__pubtech_queue_on_consent.push(function onConsent(cmpType, data) {
    const tcfData = data.consentBaseApi;
    const publisherConsentObject = data.integrations.cookieConsents;
    if (consentData.privacyLaw == 'TCF-V2-GDPR') {
       let purposeRequired;
       const purposeIdRequired = [1,2,3,4,5,6,7,8,9,10,11];
       purposeIdRequired.forEach(function start(id) {
           purposeRequired = (tcfData.purposeConsents.has(id) === true && purposeRequired !== false) ? true : false;
       })

       if (purposeRequired) {
          console.log('Cookie accepted');
       } else {
          console.log('Cookie refused');
       }

       console.log(publisherConsentObject.featureCookiesChoice); //Return true if is enabled
       console.log(publisherConsentObject.measurementCookiesChoice); //Return true if is enabled
       console.log(publisherConsentObject.userExperienceCookiesChoice); //Return true if is enabled
   }
  });
﻿
If purposeRequired is true, then the user has accepted all 11 purposes with the specified IDs. Additionally, as shown with the parameter publisherConsentObject, you can check for other types of cookies that are not related to advertising. The complete list of purposes is available here.
Be careful to avoid duplicates of the CMP script tag.
Technical cookies are always enabled by definition, so you don't need to check any flag.
Once the integration is complete, make sure to block third-party codes from using the cookies you have configured, following the tutorial﻿.
Integrate Google Consent Mode V2
The integration of Google Consent Mode V2 can be done through one of the two available integrations:
﻿GTM Integration (Consent Mode)﻿﻿
﻿Gtag Integration (Consent Mode)﻿﻿
﻿
Updated 04 Nov 2024
Did this page help you?
Configuration PubConsent
GTM Integration (Consent Mode)