---
title: GTM Fundamentals and Web Container — GTM Server-Side Module 1 — RGM Training
url: https://realgrowthmatters.com/training/gtm-server-side/gtm-fundamentals-and-web-container/
updated: 2026-06-10
source_html: https://realgrowthmatters.com/training/gtm-server-side/gtm-fundamentals-and-web-container/
---

RGM° · Training

# GTM Fundamentals and Web Container

Server-side tagging exists to solve the data-loss problem in client-side tracking. This module covers the architecture, the limitations being solved, and the 90-day migration plan.

### What you will learn

1. Why server-side tagging exists and what problem it solves
2. How web container tagging works
3. Web container architecture: dataLayer, triggers, variables, tags
4. Limitations of client-side tagging in 2026
5. The server-side alternative
6. When server-side matters most
7. The data flow: client → server → vendor
8. Common tags and their server-side configuration
9. Costs and engineering investment
10. Vendor landscape
11. The 90-day server-side migration plan

## 1. Why server-side

Client-side tag tracking (Google Tag Manager web container, Tealium, Adobe Launch) sends user data directly from the browser to vendors. Three forces have made client-side less viable: ad blockers (30 - 50% of traffic in many segments), browser tracking restrictions (Safari ITP, Firefox ETP, Chrome cookie deprecation), and privacy regulations (GDPR, CPRA).

Server-side tagging: data flows from the browser to your own server-side container, which then proxies it to vendors. This preserves data quality, gives you control, and reduces page weight.

## 2. How web container tagging works

Web container (client-side) tagging flow:

1. Page loads; tag manager script loads.
2. Event occurs (page view, click, purchase).
3. dataLayer event fires.
4. Tag manager evaluates triggers, fires tags.
5. Each tag sends data directly to its vendor.

## 3. Web container architecture

- **dataLayer:** JavaScript array of structured events.
- **Triggers:** Conditions that fire tags (page view, click, form, custom event).
- **Variables:** Data references (URL, click element, dataLayer values, cookies).
- **Tags:** Scripts that execute (analytics, ads, pixels).

## 4. Client-side limitations

| Limitation | Impact |
| --- | --- |
| Ad blockers | 20 - 50% of data lost in some categories |
| Safari ITP | Cross-domain cookies expire in 7 days |
| Chrome cookie deprecation | Third-party cookies blocked |
| Browser bot filters | Some legitimate traffic filtered |
| Page weight | 10 - 30 tags add 100 - 500ms to page load |
| Vendor outages | Slow vendor scripts slow page |

## 5. The server-side alternative

Server-side tagging architecture:

1. Page loads; minimal client-side script loads.
2. Events sent to your server-side container endpoint.
3. Server-side container processes events.
4. Server-side container forwards events to vendors via server-to-server APIs.

## 6. When server-side matters most

- High-traffic sites where data quality affects revenue decisions.
- Sites with significant ad-block / Safari traffic.
- Programs relying on Meta Conversions API, Google Enhanced Conversions.
- Sites under privacy-regulation scrutiny.
- Performance-sensitive sites.

## 7. The data flow

Browser → first-party endpoint (your domain) → server container → vendor APIs (Meta CAPI, Google Measurement Protocol, etc.)

## 8. Common tag conversions

- GA4 → GA4 Measurement Protocol via server-side.
- Meta Pixel → Meta Conversions API.
- TikTok Pixel → TikTok Events API.
- Google Ads conversion → Enhanced Conversions.
- LinkedIn Insight → LinkedIn CAPI.

## 9. Costs

- Server-side container hosting (typically $50 - $500/month at modest scale).
- Engineering setup time (40 - 200 hours initial).
- Ongoing maintenance.
- Domain configuration (sGTM subdomain or cloud-run).

## 10. Vendor landscape

- **Google Tag Manager Server-Side** (most common).
- **Stape:** Managed hosting for sGTM.
- **Tealium iQ + EventStream** (enterprise).
- **Adobe Launch / Edge Network** (enterprise Adobe).
- **Segment (Twilio):** Source-of-truth event collection.
- **RudderStack:** Open-source alternative.

## 11. Migration plan

1. Week 1 - 2: Inventory current tags and data flow.
2. Week 3 - 4: Set up sGTM instance; configure subdomain.
3. Week 5 - 8: Migrate one tag at a time, starting with highest-value.
4. Week 9 - 12: Validate data parity, deprecate client-side tags.

**How to use this module:** The architecture diagrams (Section 5), the tag conversion list (Section 8), and the migration plan (Section 11) are the planning artifacts.

### Sources & further reading

- [Google Tag Manager Server-Side docs](https://developers.google.com/tag-platform/tag-manager/server-side)
- [Stape blog](https://stape.io/blog)
- [Simo Ahava's blog](https://www.simoahava.com/)
- [MeasureSchool](https://www.measureschool.com/)
- [Optimize Smart (Himanshu Sharma)](https://www.optimizesmart.com/)
- [Analytics Mania](https://www.analyticsmania.com/)
- [Tealium blog](https://tealium.com/blog)
- [Segment blog](https://segment.com/blog/)
- [RudderStack blog](https://rudderstack.com/blog/)
- Books: Krista Seiden, *Measure Up*; Simo Ahava's GTM cookbook
- [Marketing Analytics Summit](https://www.marketinganalyticssummit.com/)
- [MeasureCamp](https://measurecamp.org/)

---

Part of the [GTM Server-Side](/training/gtm-server-side/) series · RGM Training