In this guide
- Connect Claude to the Open Tracked MCP server so it can work with your containers, domains, power-ups and Google Tag Manager.
- Give clear tasks with names, triggers and consent rules. Ask for a summary of changes.
- Keep publishing and secrets to yourself.
Claude is good at the parts of tracking work that are structured: reading a container and describing it, planning a data layer, drafting tags, explaining an error and writing a handover. With the Open Tracked MCP server, it can do those against your real set-up instead of from pasted text. This page gives practical ways to work with it. The step-by-step configuration is in the Open Tracked MCP server guide. For prompts see AI assistant prompts for tracking, and for safety see AI controls for Tag Manager.
What to connect
| Connection | What Claude can do |
|---|---|
| Open Tracked MCP server | Work with your Open Tracked containers, domains, power-ups and tracking score, and install Open Tracked tags in Tag Manager |
| Google Tag Manager (through the server) | Read containers, and create or edit items in a workspace |
| Read-only analytics servers | Answer questions from GA4 or Google Ads data |
Connected in minutes
Add your domain, install the pixel, connect your ad platforms and watch the first events land.
Session ideas
Audit a container
"Read the web container and list tags without consent settings, duplicates and naming issues. Return a table. Do not change anything."
Plan a set-up
"I run a Shopify store with Meta and Google Ads. Plan the tags, triggers and variables I need for server-side tracking. List what I must provide."
Check a set-up
"Check my Open Tracked container: tracking score, power-ups on, domain status. What should I fix first?"
Write a handover
"Write a one-page handover for this container with owners, accounts and how to test."
Give context
- Say which container, which environment and which platforms.
- State constraints: consent rules, naming convention, no new vendors.
- Ask for assumptions and for a summary of every change.
- Ask it to say when it is unsure.
Watch events arrive, live
A sample feed. In Open Tracked you see the same stream for your own store.
What to keep for yourself
- Publishing. Review in the workspace, test in Preview, publish yourself.
- Secrets. Do not paste access tokens into chats.
- Legal decisions. Consent and privacy choices need your advisor.
- Final numbers. Verify important figures in the platform.
A short example
You ask: "Create the GA4 purchase tag in the Shop web container. Name it 'GA4 - purchase'. Trigger on the custom event purchase. Require analytics consent. Work in a new workspace called claude-ga4-purchase. Do not publish." Claude creates the items, you open the workspace, read the change list, run Preview with a test order and publish when satisfied. The whole thing takes a few minutes, and you remain in control.
A realistic session
A store owner connects Claude to the Open Tracked MCP server and asks for a read-only check of the container: tracking score, power-ups on, domain status. Claude reports a score of 75, notes that Cookie Keeper is off and that the Data Store is not on, and suggests turning on both. The owner does that in the dashboard, then asks Claude to draft the Meta server tag in a new Tag Manager workspace. Claude creates it, lists every change and reminds the owner to test and publish. The owner reviews the workspace, runs Preview with a test order and publishes. The whole session takes fifteen minutes. The owner made every decision that mattered, and Claude did the typing.
Runs on your domain, anywhere
Your tracking runs on your own domain, so a visit from any country is handled the same way.
Frequently asked questions
Can Claude work with my Tag Manager?
Yes, through an MCP server such as Open Tracked's, with the permissions you grant.
Does Claude publish my container?
It should not. Ask it not to, grant only the scopes you need and publish yourself.
What is a good first task?
A read-only audit of a container.
Where is the set-up guide?
In the Open Tracked MCP server configuration guide.
Is it safe to paste tokens into Claude?
No. Keep secrets out of chats.
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.
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?
Comments
Loading comments...
