In this article, I want to tell you about a new feature from Google Tag Manager – Server-Side Tagging. GTM server-side is a hot topic right now for all marketers, website owners, and developers. The main change in this technology is moving tracking from client-side to server-side. This functionality allows you to hide business logic in the server code, speed up website loading, and improve the protection of user data by restricting access to third-party scripts.
There are two ways to collect data: client-side and server-side, both with their benefits and restrictions. Existing tag management, analytics systems, and advertising services collect data using the Client-Side Tracking method. How does it work? With Client-Side Tracking, the browser sends a request directly to a third-party tracking service like Google Analytics. The interaction takes place between two parties: the browser and a third-party service.
With Server-Side Tracking, an intermediate point is added. In this case, it is the Google Tag Manager cloud server. The request goes first to the cloud server, then the server processes this request and sends it to a third-party system (Google Analytics). It means that instead of the client browser, the request is processed by the cloud server.
Many of you saw this screenshot on Apple WWDC where they showed that Safari would start blocking 3rd party cookies on a new version of macOS. It was a shock for everyone since they showed us that Google Analytics is blocked, and you won’t be able to track the behavior of Safari users (who make around 15% of your website visitors). Even so, some say that they did not see any 3rd party pixel blocking when they installed Big Sur. This macOS is still in beta and not released to public usage. So, for now, you cannot tell how it will work on production and if there will be data protection updates in future versions. Mozilla Firefox is also blocking 3rd party cookies by default since summer 2019. If the browser blocks 3rd party cookie, you cannot follow the user all over the internet with your remarketing ads.
Nevertheless, Intelligent Tracking Prevention technology is there, and it is designed to limit website owners’ ability to track users across domains. As privacy concerns have been growing during the last several years, marketers and business owners expect the ITP technology to spread across all popular browsers and devices.
How can you prepare for Intelligent Tracking Prevention? Move from using third-party cookies to first-party cookies. And you can achieve that by integrating the Google Tag Manager Server-side container. If you set up GTM server-side on your website, AdBlockers and ITPs won’t be able to find your tracking technologies, which will lead to better data quality.
Setting up the GTM server-side is not an easy task. You’ll need various knowledge about Google Tag Manager, Google Analytics, Google Cloud, and web technology in general. Plus, your development team will be involved in this process, especially if you want to test it in the production environment.
Google offers a free test environment. But if you want to integrate it into production, you will need to pay a minimum of $120/month + additional fees that depend on the website traffic. You can use this calculator to have a more detailed estimate of how much a GTM server will cost on Google Cloud.
We created a tool that will help you set up GTM server-side container. It can be hosted either on your subdomain or our subdomain. The benefit of hosting it on a custom subdomain within the same top-level domain is that all requests will be considered a first-party cookie and prevent data loss.
2. Set up server GTM container.
4. Once you have data in the Server GTM, you can start with setting up server-side tagging. A bunch of tracking and advertising platforms support server-side tracking. You can find a list of all ss tags in this blog post and links to documentation on how to implement it.
Should you try server-side tracking? The answer is YES if you want to start collecting data about your website visitors and prepare for things like Intelligent tracking protection. And our team of experts will help!
Since Google Server-Side tracking has just been released and still has a lot to improve, you should not switch to it completely and turn off regular tracking. However, you can already take advantage of this new technology.
What cost can you expect for server Google Tag Manager hosted on Google Cloud? Is it a good idea to use a test environment on the productions site. Why stape’s hosting for server GTM is cheaper and how we secure our user’s data.Apr 1, 2021
In this article, I want to show you how to use Data Tag. This custom tag sends parameters from the Google Tag Manager Web Container to the Server Container. When used together with the Data Client for the Google Tag Manager server container, it allows sending data layer variables, custom parameters, and other data from the web to the server container. As a result, Data Client retrieves information from the Data Tag into the Google Tag Manager Server Events.Feb 28, 2021
Server-side tagging has been one of the main trends in web analytics for the last couple of years. Ad blockers, Intelligent Tracking Protection, 3rd party cookie restrictions, regulations like GDPR made analytics and advertising companies start worrying about how and what information they collect about site visitors. Server-side tagging allows moving third-party tags off your site and into a cloud server. In this case, third-party pixels are loaded directly from the could server rather than your site. In this article, I will explain and demonstrate the basics of setting up Google Tag Manager server container, server Universal Analytics, GA4, and Facebook Conversion API.