DATALYR

What is server-side tagging?

Server-side tagging runs your marketing tags in a server container you control instead of in the visitor's browser. The browser sends one request, and your server forwards the data to each platform; Google's version is server-side Google Tag Manager (sGTM).

Also called sGTM, Server-side GTM

Why it matters.

  • Fewer scripts in the browser can mean faster pages.
  • You control exactly which data leaves your domain for each platform.
  • Requests from your own domain are harder for blockers to hide.

Common mistakes.

  • Expecting it to fix attribution on its own. It still relays what the browser saw unless you feed it backend data too.
  • Forgetting hosting and upkeep: the container is infrastructure you run and pay for.
  • Sending the same conversion from browser and server without deduplication, which double counts it.

Measure it well.

DATALYR sends verified sales from your own systems to each platform, so your ads see the conversions a browser container can miss. The blog article on server-side tracking explains the difference.

Read about server-side tracking →

Questions, answered.

Contact us
  • Related, not identical. Tagging is the container that relays events; tracking is the practice of sending conversions from your own systems, such as order data from your backend.

  • Server-side Google Tag Manager: a Google Tag Manager container that runs on a server you host rather than in the browser.

  • Usually it works alongside it. Platforms typically want browser and server events paired and deduplicated.

Related terms.

See what really drives revenue.

Real-time attribution, analytics and conversions for every channel, campaign and ad, ready for your team and your agents.

Get started