Analytics for the
agent era.

One script tag records traffic, events, crashes and web vitals. You read them in a dashboard. Your coding agent reads them over MCP.

Free for 3,000 events a month. No card needed.

Example session in Claude Code, connected to Tracabit

Why did signups drop yesterday?

tracabit.query_analytics(timeframe: "7d")9,412 sessions, signups down 31%
tracabit.compute_funnel("/pricing" → "/register")14.2% → 9.1% after Tuesday
tracabit.inspect_errors(limit: 20)41 TypeErrors on /register, Safari 17

Pricing-to-signup conversion fell from 14.2% to 9.1% after Tuesday's deploy. Most of the drop is mobile Safari, where the register form throws a TypeError on submit. Fixing that error should recover most of it.

One script tag. Six things you'd otherwise stitch together.

The tracker is under 4 KB gzipped, loads after your page, and sets no cookies.

<script defer
  src="https://cdn.tracabit.com/tracabit.js"
  data-key="tcb_live_…"></script>

Traffic: Pageviews, sessions, referrers, countries and devices, rolled up by day.
Custom events: GA4-style events such as sign_up or purchase, with whatever parameters you attach.
Crashes: Uncaught errors with stack traces, file and line. Mark them resolved when the fix ships.
Web vitals: LCP, CLS, FCP and TTFB from real visitors, broken down by page.
Funnels: Pick the pages in order and see where people drop out, from real session journeys.
Daily digest: Yesterday's numbers for each project, in your inbox once a day.

Ask in plain words. Your agent runs the queries.

Tracabit is an MCP server. Connect Claude Code, Cursor or any MCP client with your project's secret key, and it can pull the numbers itself instead of you pasting screenshots into chat.

claude mcp add --transport http \
  tracabit https://api.tracabit.com/mcp \
  --header "Authorization: Bearer tcb_sk_…"

No agent? On Pro, Ask Trace answers the same questions inside the dashboard.

query_analytics: Visitors, pageviews, bounce rate, top pages, referrers, countries, devices.
inspect_errors: Recent crashes with stack traces and how often each happened.
resolve_error: Marks a crash resolved, or reopens it.
compute_funnel: Conversion and drop-off across any sequence of pages.
get_billing_usage: Events used this month, plan limits and renewal date.
list_projects: Every project the key or account can see.

Useful numbers without following people around the web.

No cookies: Sessions live in sessionStorage and end when the tab closes.
Country, not location: Events are stored with a country code. IP addresses aren't stored.
Retention you set: Choose how long each project keeps its data. Older days are deleted on schedule.
Not for sale: We don't sell visitor data or use it to train third-party models.

How Tracabit handles data

Priced by events, not seats.

Compare plans

Developer

Free

3,000 events a month and one project. For side projects and trying things out.

Starter

$8/mo

50,000 events a month across unlimited sites.

Pro

$49/mo

5 million events a month, then $0.012 per thousand. Scales with traffic instead of capping it.

From the blog

All posts

Analytics for the agent era.