Configuring Complianz for Server-side Tag Manager

Although server-side tag manager is relatively new we had some questions about how to proceed if you serve tags from the server-side, and not directly from the third-party domain There are 2 domains to consider. In this example you will see the first domain that sets the tag, and the transport URL, that receives data.

In this case, it’s both, a self-managed server for both instances. It’s however possible to still serve the tags or container with or a dedicated Google Cloud solution and still hold another transport URL.

That being said, if you’re using server-side tagging, you probably understand the differences.

					<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src=""></script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());

  gtag('config', 'G-1234', {
     transport_url: '',
     first_party_collection: true

Configuring Complianz

Complianz can add your GTM code automatically, but this is only available for standard implementation. If you want to use Complianz with your variation of server-side tagging.

Choose Google Tag Manager under “Statistics,” but make sure Complianz does not add the snippet. As shown in the below screenshots.

Afterwards you can add the desired snippet yourself and Complianz knows it should fire events through the data layer. To further  configure Tag Manager, please read this article

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