Update GTM settings to send data to server-side container
Posted: Sun Dec 22, 2024 7:11 am
server-side GTM container creation directly from Tag Manager ;
server-side custom domain verification and mapping: at the beginning of the implementation, a domain is provided, which hosts the server container, which belongs to Google (you can recognize it because it has the name appspot.com ). It will be necessary to create a tracking subdomain linked to
create Clients to process incoming requests
verify and test incoming requests
send first data from server-side container taiwan cellphone number to third-party providers
If you are using Google Cloud Platform, upgrade to the App Engine Flexible environment
publish the container, monitor costs and increase tracking over time with the aim of running client-side and server-side tracking in parallel
Regarding costs, let's say that, in addition to what was said above, you have to consider the effort to dedicate to the solution. You can't think that server-side tracking is something pre-packaged that you set up and then let it go (in reality it can't be like that for client-side tracking either).
You need to think about dedicating the right resources to maintain it, analyze the data and the differences between the information collected on the client side and the server side. This is a cost/investment that is difficult to quantify but necessary to consider.
In which cases should it be implemented?
As we have discussed, it is clear that the solution is not so difficult to implement, but at the same time not very simple either. Furthermore, it requires planning the right resources over time. I would tell you that it is a solution that, starting from medium-sized companies, must be seriously considered.
server-side custom domain verification and mapping: at the beginning of the implementation, a domain is provided, which hosts the server container, which belongs to Google (you can recognize it because it has the name appspot.com ). It will be necessary to create a tracking subdomain linked to
create Clients to process incoming requests
verify and test incoming requests
send first data from server-side container taiwan cellphone number to third-party providers
If you are using Google Cloud Platform, upgrade to the App Engine Flexible environment
publish the container, monitor costs and increase tracking over time with the aim of running client-side and server-side tracking in parallel
Regarding costs, let's say that, in addition to what was said above, you have to consider the effort to dedicate to the solution. You can't think that server-side tracking is something pre-packaged that you set up and then let it go (in reality it can't be like that for client-side tracking either).
You need to think about dedicating the right resources to maintain it, analyze the data and the differences between the information collected on the client side and the server side. This is a cost/investment that is difficult to quantify but necessary to consider.
In which cases should it be implemented?
As we have discussed, it is clear that the solution is not so difficult to implement, but at the same time not very simple either. Furthermore, it requires planning the right resources over time. I would tell you that it is a solution that, starting from medium-sized companies, must be seriously considered.