How does Server-side tracking work?
Posted: Sun Dec 22, 2024 6:52 am
In the server-side context in GTM, things change because the information does not simply pass from the user's browser to third-party tools, but a new element is added which is the Server Container that is hosted on a server that, once set up, allows us to work in a first-party context.
server side tagging google tag manager
Example of the new server-side mode
The operation is simple from a theoretical point of view, because the russian numbers basic idea is to move the HTTP requests to the server hosting the new container, manage them better there, only then send the data to the various service providers.
However, it is good to keep in mind that this type of tracking works with two containers. Oh yes! We do not think we need to archive the client-side container. Basically, we will have to manage the classic container that we have always used and the new server-side container.
To this, a new element called Client is added, which is the key tool of the whole system, because it is the connection that actually manages the incoming HTTP requests and defines them so that they can be used by the tags to complete the request in the server and then send the data to the service providers.
But be careful: when we talk about client-side we are not saying the same thing as when I refer to “Clients”.
We talk about client-side or web-side container when we refer to the container that works through the user's browser.
When I talk about “Clients” I am referring to this new element, which is essential for making server-side tracking work correctly.
server side tagging google tag manager
Example of the new server-side mode
The operation is simple from a theoretical point of view, because the russian numbers basic idea is to move the HTTP requests to the server hosting the new container, manage them better there, only then send the data to the various service providers.
However, it is good to keep in mind that this type of tracking works with two containers. Oh yes! We do not think we need to archive the client-side container. Basically, we will have to manage the classic container that we have always used and the new server-side container.
To this, a new element called Client is added, which is the key tool of the whole system, because it is the connection that actually manages the incoming HTTP requests and defines them so that they can be used by the tags to complete the request in the server and then send the data to the service providers.
But be careful: when we talk about client-side we are not saying the same thing as when I refer to “Clients”.
We talk about client-side or web-side container when we refer to the container that works through the user's browser.
When I talk about “Clients” I am referring to this new element, which is essential for making server-side tracking work correctly.