GDPR Server Tracking Is Now in Cogny: Check Your Server-Side GTM Trackers From Your Agent
GDPR Server Tracking is our hosted server-side Google Tag Manager: your tagging server runs on bare metal in the EU instead of on a US cloud. On November 9 it got its own MCP server. Cogny now connects to it directly, so the agent that reads your GA4, Google Tag Manager and ad accounts can also see whether the tracking server behind them is receiving data.
TL;DR
- Connect with one sign-in from Settings → Integrations → GDPR Server Tracking. No API key.
- Health: each tracker's setup stage, a live DNS check and its tracking traffic in the last 30 minutes.
- Stats: requests, response times, top paths and a per-minute series.
- Accounts and usage: the accounts you can open, their trackers, and monthly credit usage for the last three months.
- Changes, after you confirm: create a tracker (and get the DNS A record to add), change its size, IP anonymization or GTM container config, or delete it.
- One connection reaches every GDPR Server Tracking account your user can open.
- Included in Cogny Solo ($9/mo) and every plan above it. On the GDPR Server Tracking side the MCP server is included with every plan.
What you can ask for
| Goal | Example request |
|---|---|
| Check health | "Are all my tracking servers healthy?" |
| Explain a drop | "GA4 events dropped in the last hour. Is the tracker for shop.example.com still receiving traffic?" |
| Read traffic | "Which paths got the most requests on sgtm.example.com in the last hour?" |
| Set up | "Set up server-side tracking for shop.example.com and tell me the DNS record to add." |
| Resize | "Move the tracker for shop.example.com to the Small size." |
A tracking server answers load balancer health checks all day, so a server can look busy while no tracking data arrives. The tools report health checks separately from tracking traffic. "Healthy" means the tracker is receiving real hits.
The ten tools
| Tool | What it does | Access |
|---|---|---|
list_accounts | Lists the accounts you can open | Read |
list_server_sizes | Tracker sizes, event allowance and price | Read |
list_servers | Trackers in an account | Read |
get_server | Configuration and remaining setup steps | Read |
get_server_status | Setup stage, DNS, traffic in the last 30 minutes | Read |
get_server_stats | Requests, response time, top paths, per-minute series | Read |
get_credit_usage | Monthly credit usage for the last three months | Read |
create_server | Creates a tracker and returns the DNS record to add | Manage |
update_server | Changes size, IP anonymization or GTM container config | Manage |
delete_server | Deletes a tracker (the host name must be repeated) | Manage |
Who approves a change
Two things stand between your agent and a change to a tracker.
- The access level you pick when you sign in. With Read, the agent can look but can't change anything, whatever it asks for.
- Cogny's tool settings. In Cogny the seven read tools run without asking.
create_server,update_serveranddelete_serverask you first each time, unless you change that in the connection's tool settings.
Creating, resizing and deleting a tracker change what you pay GDPR Server Tracking, so read the confirmation before you approve it.
In scheduled reports
The Data & Tracking Quality report template now checks your trackers when GDPR Server Tracking is connected: setup stage, DNS, and tracking traffic lined up against GA4 event volume, so a drop that starts at the tracking server is told apart from one that starts in your tags or consent banner. It uses the read tools only.
Limits worth knowing
- The agent never sees your visitors' events. The tools return tracker settings, setup status, DNS results and aggregated request statistics such as counts, response times and request paths.
- GTM container contents are not part of it. Tags, triggers and variables are the Google Tag Manager integration's job; this one covers the server they run on.
- Access follows your user. The agent reaches the accounts you can open on GDPR Server Tracking, with the access you have there.
- You can disconnect Cogny at any time under MCP access in the GDPR Server Tracking account menu, or from Settings → Integrations in Cogny.
How to connect
- Open Settings → Integrations in your Cogny workspace and find GDPR Server Tracking under Analytics.
- Click Connect, sign in with your Google account and pick Read or Manage.
- Ask your agent. The tools are there in the Cogny chat and for any agent on
app.cogny.com/mcp.
Working only from your own agent, without the Cogny app? Create a personal access token under MCP access in GDPR Server Tracking and ask your agent to connect GDPR Server Tracking to Cogny with it.
No GDPR Server Tracking account yet? Sign up at gdpr-server-tracking.eu; Micro and Small start with a one-month free trial.