How Server-Side Tracking Works.
Move your tracking from the fragile browser to a secure, 1st-party server environment. Bypass ad blockers, extend cookie life, and own your data.
Browser-side tracking
Third-party scripts, each one easy for blockers and browsers to cut off.
Server-side with TagLinc
track.yourstore.com
One first-party stream to your own subdomain. Your server forwards it to each platform.
The data pipeline
From one browser request to every ad network
Three steps, all on infrastructure you control.
- Step 1The User
Browser
Customer visits your site. Instead of firing 10 different third-party pixels, your site sends ONE secure data stream to your TagLinc server using a 1st-party domain.
third-party pixelthird-party pixelthird-party pixelthird-party pixel1 first-party stream - Step 2TagLinc Server GTM
Your dedicated server
Your dedicated server processes, filters, and hashes the data. Ad blockers cannot touch this because it happens on your own subdomain (e.g.,
track.yourstore.com).ProcessFilterHash - Step 3Ad Networks
Server-to-server
TagLinc securely routes the clean, hashed data directly to Meta CAPI, Google Analytics, and TikTok via their APIs.
MetaConversions API
Google AnalyticsMeasurement Protocol
TikTokEvents API
Step by step
What happens to one purchase
Follow a single order from the shopper's browser to Google, Meta and TikTok.
- 1
The shopper buys
Your site's web Google Tag Manager container sees the purchase, with order ID, value, currency and items.
- 2
One request to your own domain
Instead of loading a pixel for every platform, the browser sends one request to your tracking subdomain, such as track.yourstore.com. To the browser and to ad blockers it is your own site.
- 3
Your server container receives it
TagLinc runs Google's official server container on that subdomain. A client in the container reads the request and turns it into an event.
- 4
Tags clean and enrich the event
Server tags decide what each platform gets: hash the email for Meta and Google Ads, drop data a vendor should not see, add the visitor's country or a stable visitor ID.
- 5
Server-to-server delivery
The server sends the purchase to GA4, Meta Conversions API, Google Ads and TikTok Events API over their APIs. Browser limits and blockers no longer decide what arrives.
- 6
You see it arrive
The live request meter shows the requests reaching your container, and Event Logs (paid plans) show each one, so you can check tracking without browser dev tools.
What you set up once
- Deploy a server container: connect Google Tag Manager and pick a plan
- Add your tracking domain: one CNAME record at your DNS provider
- Point web GTM at it: set server_container_url and publish
- Switch on Power-Ups: Custom Loader, Cookie Keeper and more
Under the hood
The technical edge
What makes the difference once the data reaches your server.
Custom Loader
Serves gtm.js from your own domain under a path you choose, so blockers that look for googletagmanager.com let it through.
Cookie Keeper
Puts back the cookies Safari deletes after 7 days, for up to 400 days (paid plans).
Zero Server Headache
Fully managed infrastructure. No Docker or Linux knowledge required.