Skip to content
$_ setuptracking

Self-Hosted Tag Manager

Pillar: alternatives to Google Tag Manager when you don’t want a Google product, a third-party CDN call, or a third-party container injecting scripts at runtime. Self-hosted tag manager options, server-side patterns, and the simpler “just write your tag inline” path.

GTM is a compromise — it’s free because Google indexes the tag behavior. A self-hosted tag manager (or no tag manager at all) keeps load orchestration on your servers. The trade-off is operational; you become the debugger when a marketing tag misfires.

Published guides

  • 7 Self-Hosted GTM Alternatives That Actually Work in 2026 — comparison of Matomo Tag Manager, Stape SS, Tealium private-cloud, Adobe DTM self-host, Piwik PRO, Tag Manager Lite, and the “just write a small loader” pattern. Cost, deploy effort, and per-event overhead for each.
  • Cloudflare Zaraz vs Self-Hosted sGTM: Which to Run — the head-to-head most teams confuse. Where the tags actually run, cost (Zaraz per-event vs a flat VPS), consent and EU data residency, the Docker-on-your-VPS path off App Engine, and when to skip both.

Cookbook entries shipping next

  • Matomo Tag Manager — install & first 5 tags — full deploy on top of an existing Matomo install. Container, version control, and rollback workflow.
  • The minimal-tag-manager pattern — for sites with <5 tags total. A single 2-KB JavaScript loader replaces the entire container concept and runs without third-party calls.
  • Server-side conversion API patterns — sending conversions to Meta, Google Ads, and X without a browser-side pixel. The plumbing, not the marketing pitch.
  • Cookieless tracking — many tag manager use-cases vanish if you’re already cookieless (no consent gating logic needed). Check this pillar before assuming you need a TMS at all.
  • Install recipes — Matomo Tag Manager rides on top of the Matomo install recipe. Set up the platform first.
  • Custom events & goals — what your tag manager fires events into. The two pillars are companions.