Skip to content
SERGE
DOCS

From the snippet to your data

Serge is built on first-party measurement: a one-line snippet records per-page-view facts — path, engaged time, deepest scroll, attribution — and the Journey Field, Ask and the weekly report read from it. These docs cover the snippet, the read APIs, the MCP server and the machine-readable resources.

What Serge is

Serge shows how visitors move through your website: live journeys built from your own snippet, lenses including AI attribution, Ask, and a weekly report. The snippet is storage-free by policy, and declined consent means no device access. Journeys never span days, and reporting gaps stay unavailable, never zero.

First-party measurement

The Serge snippet records per-page-view fields: path, engaged time, deepest scroll depth, events, attribution and device. It can also record supported acquisition markers and associate subsequent site activity with them. No source observes every click or outcome; installation, consent and event coverage bound what is recorded.

Install happens in the app under Site: copy the one-line script tag and your public token. Consent mode and a first-party proxy are available for sites that need them.

API reference · Displaying Serge analytics

MCP server

The Serge MCP server connects your LLM client — Claude, Cursor — to your Serge workspace, so you can ask about your measured traffic, journeys and sessions in plain language. Authentication is via OAuth (your Serge login) or a workspace API key.

MCP server overview · Setup guide

Machine-readable resources

For LLMs and crawlers that want the product described in their own format: llms.txt is the concise product description, llms-full.txt the extended version. Both are kept current with the product.

llms.txt · llms-full.txt

Current boundaries

Journeys are built from one day of observed page views; the daily-rotating visitor hash means no cross-day stitching. AI referral is an attribution observation, not conversation visibility, and attribution is not causation. Campaign creation is parked: campaign APIs and data remain available to existing integrations, and nothing here re-opens live ad delivery.

Questions the docs don’t answer? Contact us — we respond to every message.