Google Cloud Run vs. Stape.io for Server-Side GTM: A Comparison

What is Server-Side GTM?

Server-side GTM changes how much control you have over your data. Tags send data to your own tagging server first, instead of every vendor collecting it straight from the visitor’s browser. That means fewer third-party scripts on your site and the option to remove or change data before it reaches a vendor. It is interesting for businesses focused on data security, better data collection, website performance and compliance with data protection regulations like GDPR.

Overview of Google Cloud Run

Google Cloud Run is a fully managed compute platform that runs containers in the cloud, and it is Google’s recommended host for server-side GTM. You run two services: a preview server for GTM’s Preview mode and a tagging server for live traffic. Cloud Run adds and removes instances as traffic changes.

Tag Manager can provision Cloud Run for you automatically. That creates a new Google Cloud project with a preview server and a single tagging server, always in the us-central1 (Iowa) region, and Google says it is for testing only. For production you set up the services yourself in the Cloud Run console or with the command line, where you choose the region and the number of instances.

Overview of Stape.io

Stape.io is a specialised hosting service for server-side GTM. You paste your container configuration, pick a server location and Stape runs the servers. On top of hosting it offers “power-ups”: features you switch on in the dashboard, such as the Custom Loader, Cookie Keeper and Anonymizer. Stape.io is most interesting for teams with limited technical knowledge that still want the benefits of server-side GTM.

Comparing Google Cloud Run and Stape.io

Scalability and Performance

Google Cloud Run handles large volumes well thanks to autoscaling. Google expects 2 to 10 instances to handle 35 to 350 requests per second, depending on your tags. Its recommended setup keeps at least 2 instances running with CPU always allocated, so it doesn’t scale to zero: you pay for those instances even without traffic. Stape.io also scales with your traffic within your plan’s request limit. Plans go up to 20 million requests per month, with a custom plan above that, and from the Business plan you get multi-zone hosting that sends each request to the nearest server zone.

User Experience and Ease of Use

Stape.io stands out for its simplicity, ideal for users without deep technical knowledge. Power-ups turn otherwise technical solutions into a click of a button. The Custom Loader serves the GTM and GA4 scripts through your own domain so ad blockers interfere less. Cookie Keeper restores marketing cookies that browsers with ITP, like Safari, would delete after 7 days. Google Cloud Run, being part of Google Cloud, requires more technical knowledge (billing, regions, load balancers, logging) but offers more control and customisation.

Customization and Flexibility

Google Cloud Run allows extensive customisation, benefiting large businesses with specific needs: you choose the region and instance size, and you can deploy to multiple regions behind a load balancer. Stape.io offers a more straightforward, though less customisable, approach. The power-ups cover most of what a standard server-side GTM deployment needs.

Pricing and Cost Efficiency

Google Cloud Run is pay-as-you-go. Google recommends a minimum of 2 instances, each with 1 vCPU and 0.5 GB memory and CPU always allocated. Google puts each instance at about $45 per month, so roughly $90 per month for the minimum, plus extra instances when traffic grows. The free tier for this billing type (240,000 vCPU-seconds and 450,000 GiB-seconds per month) covers only a few days of one instance. Above about 1 million requests per month, request logging can add significant charges, so Google recommends turning it off. You can calculate the costs with the Google Cloud Pricing Calculator.

Stape.io offers a simpler pricing structure, making it easier for small businesses to predict expenses. The free plan includes up to 10,000 requests per month. Paid plans start with Pro at $20 per month ($17 billed annually) for up to 500,000 requests, followed by Business at $100 for up to 5 million and Enterprise at $200 for up to 20 million. You can calculate the costs with their Stape Pricing Calculator.

Security and Compliance

Google Cloud Run comes with Google Cloud’s security controls and compliance certifications. Stape’s Custom plan adds a custom DPA, a BAA for HIPAA and a private cluster. Both services offer server locations in and outside the EU for GDPR considerations. On Cloud Run you choose the Google Cloud region yourself (automatic provisioning always uses us-central1 in the US). Stape Europe accounts have server zones in Poland, France, the Netherlands and Italy. Stape Global accounts have 15 zones worldwide, including Belgium, Germany and Finland.

Community and Support

Google Cloud Run benefits from Google’s extensive documentation and a large community. But their support is often harder to reach. Stape.io, while smaller, offers 24/7 email and chat support from the Pro plan, call support on Enterprise and a helpdesk focused on server-side GTM.

Use Cases and Recommendations

Large enterprises with complex tagging requirements and those who already work in Google Cloud might prefer Google Cloud Run. Small to medium-sized businesses, or those with limited technical resources, might find Stape.io more aligned with their needs.

Conclusion

Choosing between Google Cloud Run and Stape.io for server-side GTM should be based on your organisation’s size, technical capabilities and specific requirements. Google Cloud Run offers scalability and full control for complex needs. Stape.io offers ease of use, ready-made features and predictable pricing for smaller organisations.

Both are solid options for server-side GTM, and the right choice depends on how well their capabilities fit your marketing strategy. Hopefully you have enough information to make your decision. Good luck with the implementation.