Google Tag Manager Server-side
Google Tag Manager server-side is a way of running Google Tag Manager on a server instead of in the browser (client-side). It can potentially have a huge impact on the way you collect data for the user. This article is not going to be a how-to guide to using Google Tag Manager server-side. Instead, it will be an outline of some of the most important advantages and concerns related to this new product.
If you are interested in a how-to guide to setting up Google Tag Manager Server-side, I can highly recommend you to take a look at the following video (25 mins) by Simo Ahava. He explains the basic steps of setting things up. If you are keen on having a more detailed way of learning how to run GTM SS, check out his online course at Team Simmer.
What is server-side tracking?
With server-side tag management, you can introduce a server on which you are able to manage the distribution of data to third parties. Instead of using a plethora of javascript trackers on a website which gives third parties a lot of freedom to collect the data they feel fits the needs of their end-users, you will be in full control to choose which data you want to share with which technology.
This server-side setup has many advantages and some concerns as well. I will discuss all of these in the following chapters.
Advantages of Google Tag Manager Server-side
Using a server-side tag management solution has several big advantages over client-side tracking. And those advantages are expected to grow over time. With all the focus on privacy and GDPR to better manage and respect the wishes of users, the way we collect and manage data will become more important over time. Also, increasing measures by providers of browsers like Apple and Firefox, to safeguard the data and rights of users, will impact the way we collect and manage data.
Reduce load on page
Up until the use of server-side tracking, we would collect data in the client (the browser). Most of the vendors would use javascript trackers to manage their data collection. This means whenever a new vendor like Google, Facebook, Affiliate would like to collect data, they would ask the developer of the website to implement a javascript library. When many of the javascript libraries would be loaded on the website, it would slow down the way the website loads. Even though over time the performance of these javascript libraries would improve, every bit counts.
With the introduction of server-side tracking, only one tracker would be introduced to the website. All the third party vendors would then receive the data through that one single item via the server. This would significantly reduce the amount of work to be done in the browser and improve the performance of the website. This is easily the biggest benefit of server-side tracking for the website owner and the end-user of the website. Speed is good :-)
Have full control of the data
When javascript libraries are added to the website to collect data, it is often not very well understand what type of functionalities are activated. Many javascript libraries collect more than you may know. Over time, the javascript library can also be updated, without the website owner knowing about it. By using server-side data-collection, you have a 100% control over all the data that you are sending to the vendor. This means no more surprise updates and reducing the risk of data leaks significantly.
Cleanup of payload
Once you have full control of the data, you can also easily control the data you are sending. You can easily redact some privacy sensitive data you may not want to share with some vendors. Consider the removing IP addresses, email addresses from url’s or other dimensions before sending the data forward.