A little more connected.
A lot more useful.
Bring your payments and your history. Take clear answers back to the tools where your team already works.
of your site.
The visit.
And what came of it.
Connect Stripe to put revenue beside your traffic. Follow payments back to the pages and campaigns that led to the checkout.
Explore revenue analytics ↗A fuller account.
Unattributed payments stay visible, so you can see where the connection to a visit is missing.
Ask where
you already think.
Give your MCP-compatible assistant access to your site’s numbers. Three focused, read-only tools make it easier to move from a question to a useful answer.
Connect with a site-scoped API key. Your assistant can read that site’s analytics without changing its settings.
The big picture
Visitors, views, bounce rate, live activity and revenue for your chosen period.
The useful details
Top pages, sources, countries and devices. Find out what is moving the totals.
The moment you’re in
How many people have been on your site in the last two minutes.
Your numbers.
Your next idea.
Bring site totals into an internal report or a tool of your own. A site-scoped key gives you authenticated access to your analytics over HTTP.
Choose a date range. Read aggregate traffic and revenue, or request a breakdown by page, source, country or device. Keep your reporting close to the work it informs.
GET /api/v1/breakdown?dim=pathAuthenticate with your site’s Bearer token.
A small update.
A shared perspective.
Send a daily or weekly digest to your Slack channel. Give your team a regular view of visitors, pages, sources and revenue, with a link back to the full picture.
Your site, in a few lines.
Daily or weekly · your chosen channelTraffic, with changes from the previous period
The pages and sources bringing people in
Revenue and a link to your dashboard
A fresh start.
With a little history.
Bring exports from Google Analytics, Plausible or Fathom. Imported visitor and pageview totals sit beside your new Pulse data, so the story doesn’t have to begin at zero.
Carry the numbers forward.
Upload a file when you’re ready. This is a one-way import, with no automatic sync or Google tracking script added to your site.
Bounce and session metrics remain based on Pulse data. Import batches can be rolled back without deleting your Pulse history.
A small setup.
A clear scope.
The API and MCP use the same read-only key for one site. Keep access close to the work, and change it from the site’s developer settings when needed.
Choose the site
Open its developer settings and create an API key. The full key is shown once, so store it securely.
Connect your tool
Use the key as a Bearer token with the REST API or MCP endpoint on your Pulse dashboard’s origin.
Keep access current
Rotate the key to replace it, or revoke it to end access. These changes also apply to tools using that same key.