Built to Be Queried, by You and Your Agents

Most analytics treats developers as an afterthought: a script tag and a closed dashboard. Datalenk is built the other way around. A real API, events you fire in one line, a first-party proxy you control, and an MCP server so you can ask your analytics questions straight from your coding agent.

What it does

• A real API: read your traffic, channels, conversions and revenue programmatically, and send events server-side. Your data is yours to query and export.
• One-line custom events: datalenk.track('plan_upgraded', { plan: 'pro', mrr: 49 }). Every event inherits the visitor's channel, campaign and link attribution automatically.
• Server-side events: fire conversions and revenue from your backend (after the Stripe webhook, for example), immune to ad blockers, which is where client-side tracking loses 40%+ of tech audiences.
• First-party proxy: serve the script and collect events through your own domain (stats.yoursite.com), for completeness and a clean data relationship with your visitors.
• MCP server: connect Datalenk to Claude Code, Cursor or Codex and ask "which channel drove the most revenue last week" from your prompt, no dashboard required.

How it works

Drop the script for client events, or hit the API/server-side endpoint for backend events. Add the MCP server to your agent config and query in natural language. Everything is documented, and the event model is the same whether the event comes from a browser, your server, or an agent.

Why this matters

DataFast shipped a CLI for agents, which proved the demand. Datalenk goes further: a full API, server-side events, first-party proxy, and an MCP server, so analytics becomes something your stack and your agents can act on, not just a chart a human glances at. For developer-heavy products, the server-side and first-party pieces also recover the large share of data that blockers strip from client-only setups.

Honest scope

The API, custom events, server-side endpoint and first-party proxy are core. The MCP server is rolling out; if it is not live in your stack yet, the API gives your agent everything it needs in the meantime, and you can request MCP priority.

Go deeper

How this powers AI traffic measurement: ↗. How events power link attribution: ↗.

Query your analytics from code, your server, or your agent. Free tier, real API. Try Datalenk free or read the docs.

FAQ

Does Datalenk have an API? Yes, a real read/write API plus server-side events, so you can query traffic, channels and revenue and send events from your backend, not just the browser.

Can my AI agent query my analytics? Yes, via the MCP server (rolling out) or the API today. Ask questions like "which channel drove the most revenue last week" from Claude Code, Cursor or Codex.

Why server-side events? They are immune to ad blockers and ideal for payment and signup events, recovering the conversions client-side pixels lose, especially with developer audiences.