Question 1

What is server-side tracking?

Accepted Answer

Server-side tracking processes analytics and marketing events on a server you control instead of in the visitor's browser. The browser sends events to your own first-party domain, and a server-side Google Tag Manager container forwards them to tools like GA4, Meta, and TikTok. This improves data accuracy, page speed, and control over what data each vendor receives.

Question 2

What is server-side Google Tag Manager (sGTM)?

Accepted Answer

Server-side Google Tag Manager is a version of GTM that runs in a server container rather than in the browser. Instead of each vendor tag firing on the page, your website sends one stream of data to the server container, which then distributes it to each vendor. This reduces the third-party JavaScript on your site and gives you control over what data leaves your environment.

Question 3

How is server-side tracking different from client-side tracking?

Accepted Answer

Client-side tracking runs vendor scripts directly in the browser, where ad blockers, browser privacy features, and short cookie lifetimes can block or shorten data. Server-side tracking moves that work to a server on your own domain, so events are more complete, pages load faster, and you decide what data is shared with each vendor.

Question 4

Does server-side tracking improve data accuracy?

Accepted Answer

Yes. Because events are sent to your own first-party domain instead of third-party vendor domains, fewer requests are blocked by ad blockers and tracking-prevention features. This typically recovers conversions and events that client-side tracking loses, which improves attribution and campaign optimization.

Question 5

Does server-side tracking make a website faster?

Accepted Answer

Usually yes. Moving vendor tags off the page reduces the amount of third-party JavaScript the browser has to download and run, which can improve load time and Core Web Vitals. The heavier processing happens on the server container instead of the visitor's device.

Question 6

What is Tracking Hippo?

Accepted Answer

Tracking Hippo is a managed, EU-hosted service for running server-side Google Tag Manager containers. You paste your GTM server Container Config, connect a custom tracking subdomain, and your sGTM container runs on managed EU infrastructure within minutes, with no Google Cloud setup required.

Question 7

Do I need Google Cloud to run server-side GTM?

Accepted Answer

No. Tracking Hippo replaces the Google Cloud setup entirely. Instead of provisioning and maintaining App Engine or Cloud Run yourself, you paste your GTM Container Config into Tracking Hippo and it runs the tagging server for you on managed EU infrastructure.

Question 8

How long does it take to set up?

Accepted Answer

Most containers are live in minutes. You create a server container in Google Tag Manager, copy the Container Config, paste it into Tracking Hippo, add a custom tracking subdomain with one CNAME record, and point your web container at that domain.

Question 9

Do I need developer skills to use Tracking Hippo?

Accepted Answer

Basic Google Tag Manager knowledge helps, but you do not need Google Cloud or server administration skills. The setup is paste-the-config, add-a-CNAME, and point your tags at the new domain. Step-by-step guides walk through each part.

Question 10

Why do I need a custom tracking domain (CNAME)?

Accepted Answer

A custom subdomain such as analytics.yourdomain.com makes your tracking first-party, which is what makes server-side tracking resistant to ad blockers and browser restrictions. Tracking Hippo gives you the CNAME target to add at your DNS provider.

Question 11

Is Tracking Hippo GDPR compliant?

Accepted Answer

Tracking Hippo runs entirely on EU-based infrastructure and keeps data processing inside the EU, which supports GDPR compliance and data-residency requirements. You also control exactly what data is forwarded to each vendor, and a Data Processing Agreement is available.

Question 12

Where is my data hosted?

Accepted Answer

All Tracking Hippo containers run on 100% EU-based infrastructure. Data processing stays within the EU, which helps with GDPR and data-residency obligations for European businesses.

Question 13

Does Tracking Hippo offer a Data Processing Agreement (DPA)?

Accepted Answer

Yes. A Data Processing Agreement is available that covers how data is processed on your behalf, so you can document your compliance with GDPR.

Question 14

Does server-side tracking remove the need for cookie consent?

Accepted Answer

No. Server-side tracking changes where data is processed, not whether you need consent. You still need a valid legal basis and, where required, user consent before collecting and forwarding personal data. Server-side setups make it easier to enforce those choices because you control what data is shared.

Question 15

How much does Tracking Hippo cost?

Accepted Answer

Tracking Hippo costs €15 per container per month excluding VAT, billed per started day at €0.50 per container per day. There are no tiers and no request limits beyond a Fair Use Policy, and new accounts start with €10 in free trial credit.

Question 16

Is there a free trial?

Accepted Answer

Yes. New accounts get €10 in free trial credit with no credit card required, so you can set up and test a container before adding any funds.

Question 17

How does billing work?

Accepted Answer

Billing is prepaid and usage-based. You add funds to your balance, or enable auto-recharge, and the daily container charge is deducted from that balance for each day a container is active. There are no tiers and no long-term commitments.

Question 18

Are there limits on requests or events?

Accepted Answer

No hard request limits apply. Containers handle unlimited requests under a Fair Use Policy, so you are not charged per event or hit and you will not get surprise overage bills.

Question 19

Which tools and platforms work with Tracking Hippo?

Accepted Answer

Anything you can run in a server-side GTM container, including GA4, the Meta Conversions API, the TikTok Events API, Google Ads, and other server-side tags. Your web container sends events to your Tracking Hippo domain, and the server container forwards them to each vendor.

Question 20

Does Tracking Hippo work with WordPress and WooCommerce?

Accepted Answer

Yes. WordPress and WooCommerce sites can use the GTM4WP plugin and point the server-side container URL at your Tracking Hippo custom domain to send events through your own first-party endpoint.

Question 21

Can agencies manage multiple clients?

Accepted Answer

Yes. Tracking Hippo is built for agencies, with multi-client workspaces so you can host and manage a separate server container for each client from one account.

Question 22

Can I use Tracking Hippo with a custom-built website?

Accepted Answer

Yes. Any website can use server-side tracking by pointing the Google tag's server_container_url at your Tracking Hippo domain. This works regardless of your tech stack, including React, Vue, and custom backends.

Server-side tracking and sGTM, answered

Server-side tracking basics

Tracking Hippo product and setup

Privacy and compliance

Pricing and billing

Integrations and use cases

Still have a question?