How to set Google Tag Manager after Consent (and is it needed?)

Complianz is investigating, just like we did with Google Fonts and reCAPTCHA, what happens when an empty container of Google Tag Manager is loaded prior to consent and how Google processes this data. Our starting point is the below statement from Google regarding Tag Manager specifically. When our investigation ends, you will find a notification in our plugin.

In order to monitor system stability and performance, Google Tag Manager may collect some aggregated data about tag firing. This data does not include user IP addresses or any user-specific identifiers that could be associated with a particular individual. Other than data in standard HTTP request logs, all of which is deleted within 14 days of being received, Google Tag Manager does not collect, retain, or share any information about visitors to our customers’ properties, including page URLs visited. Source Tag Manager Help

A much referenced article by: Klaus Meffert, Dr. GDPR blog, link: https://dr-dsgvo.de/google-tag-manager-ist-eine-cookielose-domain is also considered during this process. The main question derived here is; does a cookie-free domain constitute the necessity to stay cookie-free, or is it possible to enable a hybrid option whereby cookies are set when consented services in the container are fired, not by Tag Manager itself, but the services it delivers. If so, this opens an interesting discussion about data processing and Google’s own underlying structure with Consent Mode.

If you want to fire Tag Manager only on consent, please see below quick guide.

Loading Google Tag Manager after Consent

This will only take 2 minutes. You will need to change an answer in the wizard and add the Tag Manager snippet below:

1. Do not allow Complianz to set Tag Manager

In the wizard, under Consent – Statistics, please acknowledge the use of Google Tag Manager. Proceed to Statistics – Configuration and answer the following question as shown below:

2. Add the Google Tag Manager snippet

Add the Google Tag Manager snippet with these attributes:

  • type=”text/plain” -> This will block Tag Manager prior to consent
  • data-category=”statistics” -> This will release Tag Manager

We recommend, contrary to Google, to set it in the footer.php of your child’s theme or with a plugin like Header Footer Code Manager. And that’s it.

				
					<!-- Google Tag Manager with Consent -->
<script data-service="googletagmanager" data-category="marketing" type="text/plain" data-category="statistics">
(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-XXXXXX');</script>
<!-- End Google Tag Manager with Consent-->
				
			

Need support for Google Consent Mode V2, or TCF? Start here with our dedicated support team.

Join 1 Million users and install The Privacy Suite for WordPress locally, automated or fully customised, and access our awesome support if you need any help!