From the course: Learning Google Tag Manager

Server-side vs. client-side tags explained - Google Tag Manager Tutorial

From the course: Learning Google Tag Manager

Start my 1-month free trial

Server-side vs. client-side tags explained

“

- [Instructor] One of the new options when you create a new container is a server-side container. Now, this is a little bit different from the way GTM normally works. In the usual way, all the scripts are downloaded and then they're run on the browser, as we explained earlier in the chapter. In the server-side container, you're going to configure a server that's going to interface with your container, and then the server's going to communicate with all the various places you want to send the data. This can provide some additional control for advanced users, potentially improve security and reduced browser load times. However, it doesn't support all tags, it may incur costs, and it's definitely an advanced implementation. So it's well outside the scope of this course. Google actually recommends that even if you want to move to server-side, that you implement your container in the normal way first and then migrate over where possible and where the tags are compatible with server-side. So in that way, even if your end goal was to run server-side, it still makes sense to proceed with the examples in this course as presented so you can fully configure your account first in the standard client-side way. So while server-side tagging won't affect us here in this course, I wanted to make sure you had some context about what it was in case you come across that term being used while you're diving into the world of Google Tag Manager.

Contents