Server-Side GTM Glossary: Server GTM, CAPI, EMQ and More
In one line: server-side GTM (sGTM) moves your tags from the visitor's browser to a server you control: the browser sends events to your own subdomain, a server container receives them with a client, and tags send them on to Google Analytics, Meta, TikTok and Google Ads. The terms below are the ones you meet while setting that up, each with a link to the guide that goes deeper.
The setup
Server-side GTM (sGTM)
Google Tag Manager running on a server instead of only in the browser. Your site sends events to the server, and the server forwards them to ad and analytics platforms. See What is server-side GTM?
Web container
The normal GTM container that runs in the visitor's browser (GTM-XXXXXXX). In a server-side setup it collects events and sends them to your server instead of straight to Google or Meta.
Server container
The GTM container type that runs on your tagging server. It has clients, tags, triggers and variables, but no browser code. You publish it in Tag Manager like a web container.
Tagging server
The machine (or Cloud Run instance) running the server container, using Google's Docker image. A host such as TagLinc runs it for you. See Self-host vs managed hosting.
Preview server
A second copy of the same image, started in preview mode, that powers Tag Manager's Preview for the server container. Google says to run exactly one.
Container config
The long CONTAINER_CONFIG string Tag Manager gives you for a server container. The tagging and preview servers need it to know which container they run. See Get your GTM container config.
Client
The part of a server container that recognises incoming requests and turns them into events. The GA4 client claims GA4 requests (/g/collect); the Web Container client serves gtm.js from your domain; a Measurement Protocol client takes server-to-server hits. Without a client claiming it, a request does nothing.
Tag (server)
Sends an event somewhere: the GA4 tag to Google Analytics, the Meta Conversions API tag to Meta, and so on. It fires on a trigger, usually "Client Name equals GA4".
Requests and loading
Tracking domain (first-party domain)
The subdomain of your own site that points at the tagging server, such as track.yourstore.com. Requests to it look first-party to the browser, and only on it can the server set long-lived cookies. See Custom first-party tracking domains.
Transport URL / server_container_url
The setting on the web container's Google tag that sends GA4 events to your tracking domain instead of to Google. It is the one switch that makes GA4 server-side. See GA4 server-side tracking setup.
gtm.js and Custom Loader
gtm.js is the script that loads your web container. Served from your tracking domain (and, with TagLinc's Custom Loader, from a path of your choice), it is blocked less often than from googletagmanager.com. In our dev store test it came back in 65 ms once cached on the server.
/g/collect
The path GA4 events are sent to. With server-side GTM it is https://your-tracking-domain/g/collect, and the GA4 client claims it.
Request (quota)
One HTTP call to your tagging server: an event, a gtm.js load, a cookie refresh. Hosting plans are sized in requests a month; a store averages about one request per GA4 event. See Monthly request limits and quota.
Measurement Protocol
Google's way to send GA4 events from a server instead of a browser, for example a paid order sent from your shop's backend. TagLinc's WooCommerce plugin uses this route for its server copy of each paid order.
Events and IDs
dataLayer
The list on the page that your shop pushes events into (view_item, add_to_cart, purchase) for GTM to read. Plugins such as TagLinc's WooCommerce plugin or GTM4WP fill it.
event_id and deduplication
One ID per event, shared by the browser copy (Meta Pixel eventID) and the server copy (Conversions API event_id), so Meta keeps one and discards the other. For purchases the order number works well. See Meta Pixel and CAPI deduplication.
Conversions API (CAPI)
Meta's server-to-server way to receive events, next to the browser Pixel. With Server GTM, the Meta Conversions API tag in the server container sends them. See Meta Conversions API with server-side GTM.
Events API
TikTok's equivalent of the Conversions API. See TikTok Events API with server-side GTM.
UET Conversions API
Microsoft Ads' server-to-server way to receive conversions, next to the browser UET tag. Send the same event_id from both so each conversion counts once. See Microsoft Ads server-side tracking.
Enhanced conversions
Google Ads' way to match conversions using hashed customer data (email, phone). See Google Ads enhanced conversions with server-side GTM.
Event Match Quality (EMQ)
Meta's 0 to 10 score for how well the customer details on your server events let it match them to people. Hashed email and phone, fbp, fbc, IP address and user agent raise it. See Meta Event Match Quality.
Click IDs (gclid, fbclid, ttclid)
IDs that Google, Meta and TikTok add to the landing URL when someone clicks an ad. Sending them with the conversion lets the platform credit the right ad. Some browsers (Safari and Brave in private mode) strip gclid from the landing URL; TagLinc's Click ID Restorer brings it back in the server container from a backup parameter you add in your ad account. See Click ID Restorer.
Cookies and privacy
First-party cookie
A cookie set for your own site's domain. Browsers treat these far better than cookies from other domains.
ITP (Intelligent Tracking Prevention)
Safari's tracking protection. Among other things, it limits cookies set by JavaScript to about seven days, so a returning Safari visitor can look new. Cookies set by your own server on your own domain last longer.
_ga
Google Analytics' client ID cookie, set by JavaScript in the browser. In the GA4 client this is the JavaScript managed option, and it works on any tracking address.
FPID
A client ID cookie set by the server (HttpOnly) when the GA4 client is Server managed. It only works when the tagging server is on your own domain: in our test the server set FPID for the store's domain from a different domain, and the browser dropped it.
_fbp and _fbc
Meta's browser ID and click ID cookies. Sending them with Conversions API events raises match quality.
Cookie Keeper
A TagLinc Power-Up that re-sets chosen cookies (such as _ga and _fbp) from your own domain so they survive Safari's limits. On a live store we checked, its cookie was set for 400 days. See Cookie Keeper setup.
Consent Mode v2
Google's way for a page to tell tags what the visitor allowed, with four signals: analytics_storage, ad_storage, ad_user_data and ad_personalization. See Consent Mode v2 with server-side GTM.
gcs and gcd
Parameters on every GA4 request that carry the consent state to your server. In our tests, everything allowed gave gcs=G111 and everything declined gave gcs=G100.
Cookieless ping
What GA4 sends in Consent Mode's advanced mode when analytics is declined: an event without cookies, which Google uses for modelling.
Ecommerce terms
COD Order Protection
A TagLinc Power-Up that holds cash-on-delivery purchases in the server container and sends them to ad platforms only when the order is confirmed or delivered, so fake and cancelled orders do not train your ads. See COD Order Protection.
Server copy of an order
A purchase sent from your shop's server when an order is paid, in addition to the browser's. It counts buyers who never return from a payment page (bKash, SSLCommerz, PayPal). Both copies share one event_id, so it is not counted twice.
Related reading
Open a support ticket from your dashboard and include the container name.