Server-side tracking
.png)
Server-side tracking is a four-part series that guides you through the key steps of implementing server-side tracking in practice. We start with the foundations: where to run your server, how Cloud Run compares to solutions like Stape, and what you need before deployment. In the following parts, we will cover proper frontend GTM setup, server monitoring and maintenance, and advanced use cases such as anonymous tracking through your own server.
If you are considering server-side tracking, you will face the question of where to actually run it sooner or later. Stape, your own Cloud Run setup, or a completely different path? For some, Stape makes sense. For others, their own Cloud Run setup in Google Cloud Platform is the better option. And that is exactly what we will focus on in this article. We will go through the differences between Stape and Cloud Run and look in detail at everything you need to deploy server-side tracking on Cloud Run. We will focus on the things that are often missing from standard tutorials: how to name your servers, which region to choose, how much does running the server cost, when a load balancer is worth it, and how not to get caught out when choosing the billing type.