Send GA4 events server-side
Updated July 2026 · 1 min read
Route Google Analytics traffic through your TagVolt container so GA4 events are sent from your own domain instead of straight from the browser.
How it fits together
Your website's Google tag sends hits to your tagging server, where a GA4 client picks them up and a GA4 tag forwards them to Google Analytics. Almost all of this is configured in Google Tag Manager at tagmanager.google.com — TagVolt's role is hosting the server container and serving it from your domain.
Before you start
- A running container — see Create your first container.
- Ideally your own subdomain connected, so tracking runs first-party — see Add your custom domain.
Set up the server container
- Open your server container in Google Tag Manager and check its Clients — new server containers include a GA4 client by default.
- Add a Google Analytics: GA4 tag and set it to fire on events claimed by the GA4 client.
- Publish the server container.
Point your website at the server
In your web container, edit the Google tag and add one configuration parameter:
# parameter value
server_container_url https://tags.yourstore.com
Use your TagVolt domain as the value — or your container's default TagVolt URL while you're still testing. Publish the web container and GA4 traffic starts flowing through your server.
Verify
Open your container's Preview mode and load your site — requests should arrive and be claimed by the GA4 client. In GA4's Realtime report, events keep appearing as usual.
Events missing after the switch? Walk through Events not showing up — it covers the common causes in order.