Open Tracked/Blog/Server side tracking misconceptions

Server side tracking misconceptions

Misconceptions about how it works cause more trouble than myths about what it does. Here are eight, cleared up.

Start freeJump in ↓

4 min read · Updated October 26, 2026

ServerFirst-partyDataFailure
In this guide
Key takeaways
  • A tagging server is a computer that runs your Tag Manager container. It does not store your customers' data unless you ask it to.
  • "First-party" means your own domain. It does not mean the data never reaches vendors.
  • If the server fails, events are lost, so monitoring matters.

Myths are about claims. Misconceptions are about understanding: how the thing works inside. They lead to bad set-ups and bad conversations with clients and lawyers. This page corrects eight common ones. It complements server-side tracking myths and how server-side tracking works.

Eight misconceptions

Symptom"The server stores all my visitors' data"
Likely causeIt is a pass-through. It receives events, runs tags and forwards them. Storage happens only if you add it, for example with a data store.
FixKnow what you store. Open Tracked's Data Store keeps only what you switch on, for the days you choose, up to 400.
Symptom"First-party means private"
Likely causeThe browser talks to your domain, but your server still sends data to Meta, Google and others.
FixDecide what each vendor receives, and tell visitors.
Symptom"My data is hidden from the platforms"
Likely causeYou send them what you choose. Platforms still receive it.
FixMinimise the fields. See transformations.
Symptom"A tagging server is a CDN"
Likely causeA CDN caches files. A tagging server runs logic for each request.
FixThey can work together: a CDN in front, the server behind.
Symptom"The Tag Manager server and my website must be on the same host"
Likely causeThey are separate. The server just needs a subdomain pointing to it.
FixSee DNS configuration.
Symptom"It is set and forget"
Likely causeTokens expire, sites change, platforms update.
FixUse a weekly check. See post-launch guide.
Symptom"If the server is down, tracking falls back to the browser"
Likely causeIt does not unless you built that. Events to a dead server are lost.
FixMonitor, and keep the pixel for key events with a shared event ID.
Symptom"Hashing makes data anonymous"
Likely causeA hash can still identify a person when matched.
FixTreat hashed e-mail as personal data.
Try it

Works with your stack

Grab a logo and throw it. These are the tools Open Tracked already talks to.

Grab one. Throw it.

Who can see what

WhoSees
The visitor's browserRequests to your tagging subdomain
Your tagging serverThe events and request data, such as IP and user agent, unless you anonymise the IP
Your hostOperates the server under your agreement; check its terms and sub-processors
Each vendorThe data you send it

Data ownership and exit

The container is yours: you can export it and move it. The tagging subdomain is yours. Data you send to vendors is governed by their terms. Data in a store on your host is governed by your agreement, so ask how to export and delete it. Open Tracked containers are standard Tag Manager exports, and Data Store entries can be removed.

For online stores

Orders from your store, back to the ad that earned them

Your store sends the order once. Open Tracked passes it on to each ad platform, cleaned and deduplicated.

What to tell a client or a lawyer

  • What data reaches the server and what leaves it.
  • Where the server runs and who operates it.
  • What is stored, for how long and why.
  • How consent is applied.
  • How the client can exit.
0 of 5 done
Check your setup

Check your tracking in one pass

This is an example. Run the check on your own site to see where yours stands.

Frequently asked questions

Does a tagging server store my visitors' data?

Only what you configure it to store. By default it passes events through.

What does first-party mean?

The browser talks to your own domain. Data still goes on to vendors.

What happens if my server goes down?

Events sent to it are lost. Use monitoring and keep the pixel for key events.

Is hashed data anonymous?

No. It is still personal data.

Can I move my server container?

Yes. Containers are standard exports, and the subdomain is yours.

Do I need spreadsheets to read my results?

No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.

Is Open Tracked different from Open Track or Open Space Track?

No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.

Fix your tracking at the source

Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.

Start freeMore in Blog →
Open Tracked
Written by

The Open Tracked team

We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?

Write to us Read the docs

Was this article helpful?

Comments

Loading comments...

Keep reading

Server side tracking
Blog · 5 min read

Server side tracking myths

Server side tracking
Guides · 5 min read

Server side tracking for agencies

Server side tracking
Guides · 6 min read

Server side tracking events

Turn better tracking into better marketing performance

Start free