Changelog

What shipped, and when.Every change, dated.

New features, improvements and fixes in Highseat, newest first. Each entry has its own page.

  • Install & API

Connect Claude to Highseat by signing in

Terminal
claude mcp add --transport http highseat https://mcp.highseat.com/mcp

An app that speaks MCP can now connect to Highseat with nothing but the server URL. Add https://mcp.highseat.com/mcp to Claude, Cursor or another client, sign in, and choose the workspace, the sites it may reach and what it can do. There is no key to copy.

A connection reads by default. An owner or admin can also let it make changes, as a write API key does.

Your connected apps are listed in Workspace settings, under API keys. Disconnecting one stops it within a minute, and a connection also stops when the person who made it leaves the workspace.

  • Data

Import your DataFast history

Paste a website API key from DataFast into a site's Data settings, and Highseat reads your history through DataFast's API. It fills in every day before your first tracked one: totals, pages, sources, locations, devices, browsers, operating systems and goals.

Days the site already tracked or imported are skipped, so nothing counts twice. A year of history takes about 1 hour 10 minutes and runs in the background. The key is stored encrypted during the import and deleted when it ends.

DataFast's breakdowns hold visitors alone, so a filtered report shows visitors for those days, with no sessions, views or bounce rate. Revenue stays in DataFast.

History that DataFast imported from Plausible comes back only as totals, countries, browsers and operating systems. If you still have the Plausible export, upload it first, and the DataFast import skips those days.

Improvements

  • Bounce rate and session time read "–" in the stats above the chart and in the tables when no session counts.
  • In the public API, bounceRate and avgDuration are null when no session counts, so check that your code handles it.
  • Dashboard

Put a chart or a single number on any page

The Embed this chart dialog: options for a chart or a figure, the metric, the period, the theme and a transparent background, beside a live preview of a visitors chart for the last 30 days.

Show your traffic on your own site: a public stats page, an advertise page, a line in your footer. Click Embed… in the dashboard's toolbar, pick the main chart or a single figure, choose the metric and the period, and copy the code. A figure can be visitors, views, revenue or who's online now.

The card reads live data and fits itself to your page, in light or dark. Last 30 days stays the last 30 days, so it moves with the calendar and matches your dashboard.

Each embed has its own link, and that link shows the one chart or figure you picked. Anyone reading your page's source gets that card and nothing else from your dashboard. Filters you've set carry over, so a chart can show one country or one campaign.

Your embeds are listed in a site's Sharing settings. Delete one and it disappears from every page that shows it. The embed guide has the details.

Improvements

  • A dashboard embedded from a share link now sizes its frame to fit, so your page shows no second scrollbar and no empty space.
  • Embeds take a transparent background, so your page's own colour shows through.
  • Revenue

Revenue from Stripe payments outside Checkout

A payment taken with Stripe Elements, or a PaymentIntent your own code confirms, now counts as revenue. Highseat waits about ten minutes before recording it, so a payment that also belongs to a Checkout session or an invoice is never counted twice. The PaymentIntent's description becomes the product name.

A webhook connected earlier needs one more event. Open the endpoint in the Stripe Dashboard and add payment_intent.succeeded. The URL and the signing secret stay the same.

Improvements

  • Drag a funnel's steps or a report's series to reorder them.
  • An install card that waits for the first pageview says when your own browser is blocking the tracker, so you know the install may be fine.

Fixes

  • A property filter on event counts, goals and the chart counts only the events that carried the value, not every event of a session that had one.
  • Dashboard

Put your sites in your own order

A workspace's site cards on All sites, with a site's actions menu open on Move to top and Move to bottom.

Drag a site on All sites to where you want it, in the card grid or the list. The order is yours alone: other members of the workspace keep their own. A site's ••• menu has Move to top and Move to bottom too.

The site switcher follows the same order, and keys 1 to 9 open your first nine sites from anywhere in the app.

Improvements

  • The date picker has a Show by switch, so a chart reads by hour, day, week or month. Press B to change it.
  • A funnel draws its steps as bars, with the ribbon one switch away.
  • A saved list report can rank by an event property.
  • A consumer on a paid plan can withdraw from the contract within 14 days on the Billing page, and gets back the unused days.
  • AI
  • Dashboard

See which AI assistants use your MCP server

The Assistants page of a sample site: 6.6K tool calls, a 2.1% error rate, 749 ms p95 latency and 6.9% empty results, a bar chart of calls by day, and tables of calls by assistant and by tool.

If your site runs its own MCP server, assistants like Claude and ChatGPT call its tools to answer their users. The new Assistants page shows those calls: how many, how many failed, how long they took and how often a tool found nothing. Below that, calls are split by assistant and by tool.

To record them, update the highseat package to 0.6.0 or later and call trackToolCalls(server) from highseat/mcp once, before you register any tool. It works with servers built on the MCP TypeScript SDK v2. Tool arguments, results and the caller's IP address never leave your server.

A call counts as an event on your plan, never as a visitor.

Visits that assistants send

mcpLink(url, context) tags a link a tool returns with utm_source and utm_medium=mcp. Highseat reads those visits as the AI channel, so the goals and revenue that follow belong to that assistant. The Sources card at the bottom of the page lists them.

  • Install & API

Track events from your backend

route.ts
import { track } from "highseat/server"export async function POST(request: Request) {  const user = await createAccount(request)  track("signup", { plan: "pro" }, { request, userId: user.id })  return Response.json(user)}

highseat/server records events from your own code: a server action, a route handler, a webhook handler or a job. An event that never reaches the browser now reaches your dashboard, and an ad blocker can't stop it.

track() takes the same names and properties as in the browser, typed the same way. Pass the request you are handling, and the event gets the visitor's country and device from it. Pass a userId and it counts as that user.

Set HIGHSEAT_SITE and HIGHSEAT_SECRET from your site's Installation settings on the server. track() returns at once and never throws. Events go out in batches, retry on their own, and carry an id, so a retried batch is stored once. In a serverless function, pass waitUntil so the send outlives the response.

Update the highseat package to 0.5.0 or later to get it.

Improvements

  • beforeSend changes or drops each event in the browser before the tracker sends it. Return null to drop one.
  • The tracker no longer measures scroll depth, which no report read, so it's lighter on every page and down to 2,894 bytes gzipped.
  • Goals and the Events card count people by user id, as funnels do, so one person on two devices counts once.

Fixes

  • The query parameters to keep setting is gone. Only the raw export read those values, so Highseat now drops every query string.
  • Install & API

Make changes through the API

Terminal
curl https://api.highseat.com/v1/sites/example.com/goals \  -H "Authorization: Bearer hs_live_…" \  -H "Idempotency-Key: 7f3c2a10-3f4e-4b7e-9d21-1c6a0e5b8f42" \  -H "Content-Type: application/json" \  -d '{"name":"Signup","type":"event","match":"signup"}'

The API used to read only. A write key can now make the changes an admin makes in the dashboard: create sites, change their settings, and manage goals, funnels, saved reports, chart notes and share links. It can also start a raw export.

Choose a key's access when you create it in Workspace settings, API keys. Every key made before writes existed stays a read key. Give a script a write key only when it changes something, and limit it to the sites it changes.

Send an Idempotency-Key header with a POST to make a retry safe. For 24 hours, a retry with the same key and the same body writes nothing and answers what the first call did.

  • AI
  • Install & API

Ask an AI assistant about your stats

Terminal
claude mcp add --transport http highseat https://mcp.highseat.com/mcp \  --header "Authorization: Bearer hs_live_…"

Highseat now runs an MCP server, so Claude Code, Cursor, Claude Desktop or another MCP client can read your stats. Ask "What were my top referrers last week for example.com?" and the assistant answers from the same reports as the API.

Connect it with an API key from Workspace settings, API keys. The assistant sees only the sites that key reaches, so limit the key to the sites you want it to read. Every tool reads, and none changes anything.

The server is at https://mcp.highseat.com/mcp, and it is listed in the MCP Registry as com.highseat/mcp.

  • Revenue

Revenue credit reaches the visit that found you

The Attribution card on the Revenue page with its menu open: Last touch selected under Model, and 90 days selected under Lookback, beside sources such as Google and openalternative.co.

Your attribution figures changed with this release, because three rules now give credit further back. Past sales are worked out again under the new rules.

Direct gets credit only when every visit before a sale was direct. A trial user who found you through Google and paid after typing your address in now credits Google, under Last touch, First touch and Linear alike.

When you identify a buyer, all of their sessions inside the lookback count, on any device. First touch can now reach the visit that brought them in, weeks before they signed in.

The default lookback is 90 days, up from 30. New sites start there, and sites still on 30 moved to 90. You can change it in a site's Revenue settings, or try another value on the Attribution card for one view.

Improvements

  • Tracker purchases, webhook sales and refunds convert at the exchange rate of their own day, so a delayed delivery stores the same amount.
  • A Stripe dispute now comes off the order when the funds are withdrawn, and goes back on if they are reinstated. Add charge.dispute.funds_withdrawn and charge.dispute.funds_reinstated to a Stripe webhook connected earlier.

Start with 14 days free.No card required.