Getting started, step by step
Here is how to set up each part, in order. Most teams are done in about 30 minutes.
You only need the first 5 steps to start getting alerts.
- 1 minute
Step 1: Sign in with Google
Go to the sign-in box on our home page. Click Continue with Google.
Google asks if you are OK to share your name, email and photo. That is all we ask for now.
- 1 minute
Step 2: Use your invite code
During the beta, you may need an invite code the first time you sign in. Paste it in the Beta invite code box, then sign in.
Did a teammate invite you? Then leave the box empty. You join their team when you sign in.
No code yet? Email jake@citamark.com and ask for one.
- 1 minute
Step 3: Let us read your containers
After you sign in, you land on the Overview page. Click Connect containers. Then click Connect Google.
Google asks you to let us see your containers. This is read-only. We can look, but we can't change anything.
Use a Google account that can see your containers in Google Tag Manager.
- 2 minutes
Step 4: Pick the containers to watch
You now see each account and its containers. For each one you want:
- Tick the box to watch it.
- Pick a client, or pick New client and type a name.
- Check the site address. We use it to set up browser checks for you.
Click Watch selected containers. The first look runs within a minute. For now, we watch web containers only.
- 3 minutes
Step 5: Connect Slack
On the Overview page, click Connect Slack. You can also find it under Settings, then Slack.
- Say yes in Slack. You come back to our app.
- Pick a default channel and click Save. Alerts go there unless a client has its own.
- Click Send test message to make sure it works.
- Under A channel per client, pick a channel for each client. Click Save client channels.
No Slack? That is OK. Every alert also shows on the Alerts page in the app.
- 5 minutes
Step 6: Set up browser checks
Open a container from the Overview. On its page, click Set up checks.
Did you add a site address? Then you will see a few checks we made for you. If not, add the address, then click Suggest checks.
To add your own, click New check. Give it a name and a page address. Add steps if you need them, like click or type. Then say what should happen, like a lead event being sent.
Click Create check. Then click Run now to try it.
- 3 minutes
Step 7: Turn on drop alerts for key events
On a container's page, click Set up anomalies. Then click Allow Analytics access. This is read-only access to Google Analytics.
- Pick the Google Analytics property for that site. Click Save property.
- Tick the key events you care about, like purchase or generate_lead. You can pick up to 20.
- Click Save and turn on checks.
Don't see your events? Mark them as key events in Google Analytics first, then reload the page.
- 5 minutes
Step 8: Add the monitor tag (optional)
The monitor tag counts which of your tags fire for real visitors. You don't have to use it.
- On a container's page, click Set up the monitor tag. Then click Turn on the monitor.
- Click Add the tag to a workspace for me. The first time, you may need to click Allow editing in Tag Manager.
- We put the tag in a draft space in your container. We never publish it.
- Open that draft in Google Tag Manager. Check it, then publish it yourself.
You can also copy the tag from the page and add it by hand.
- 2 minutes
Step 9: Connect your AI helper
Click MCP in the top menu of the app. Under Create a token, give it a name and tick its containers. Click Create token.
Copy the token now. We show it only once. Then add it to the AI tool you use:
- Claude Code: click Copy command, paste it in your terminal and press Enter.
- Cursor or Claude Desktop: open Connect an agent on the MCP page. Copy the setup text for your tool. Put in your token, save, and restart the tool.
- Other tools: VS Code with GitHub Copilot, Windsurf, Gemini CLI and OpenAI Codex CLI work too.
Want it to draft fixes, too? Click Grant edit permission when the app asks. Read more about bringing your own AI.
- 2 minutes
Step 10: Do your first rollback
A rollback makes an older version live again. Here is how, for when you need it.
- On a container's page, click Version timeline. Open the version that worked.
- Click Roll back to this version. The first time, click Grant publish permission and say yes in Google.
- Read what will change on the live site.
- Click Publish version 41 again, with your version number. It goes live within a few minutes.
You can only go back to versions we saved. We save each one from the day you connect.
Ready when you are
It is free while we are in beta. Start with step 1, and add the rest as you go.