Skip to content
GetProfit
Log in

← All terms

Server-side tagging

Server-side tagging is a setup where a site sends tracking events to a server container the store controls, which decides what goes to Google, Meta and others.

How it works

In the usual setup a Google Tag Manager container on the page sends each event straight to every platform, one request per destination. With server-side tagging the page keeps a web container, but it sends one request per event to a server container. That container runs in the store’s own Google Cloud project or another environment, and Google strongly recommends serving it from the store’s own domain. Its tags then build the requests for Google Analytics, Google Ads, Meta and others.

Google names three gains: less code and fewer requests in the browser, so faster pages; the chance to remove personal data before it leaves; and the chance to validate and correct events. The server can also enrich an event on the way, for example by adding the order’s profit. That lets you send profit instead of revenue and bid on POAS.

The server works only with what the page sends it. If the web container never fires, there is nothing to forward.

Where you see it

In Google Tag Manager, as a separate server container next to the site’s web container.

Not to be confused with

  • Google tag gateway — serves Google’s tag from the store’s domain and forwards its requests to Google; no tags of your own run on the way. For the most durable tagging setup, Google recommends both; our comparison shows what each one recovers.
  • Conversions API — Meta’s receiving end for events sent from a server. A server container is one way to send to it.

Right and wrong readings

  • Wrong: “After moving to server-side tagging, our conversions are right.” Right: the server forwards what it receives. A purchase counted twice or sent with a fixed value reaches Google the same way, unless you set the container to change it.

Sources