Support

Run npx satsu-analytics init in your project, or paste one script tag into your site's HTML. The tracker is under 3 KB and needs no build step. See /docs/install.

It detects your framework, adds the Satsu component and one environment variable, shows you the diff of what it changed and asks first. In an unsupported or undetected project it prints the script tag and the matching docs link instead of writing code. See /docs/cli.

Open your site, then look in your browser's Network tab for a POST to track.satsu.pro/e that answers 202. The Live count in your dashboard also picks you up within a few seconds. See /docs/verify.

First check that data-site matches your site ID, because a wrong or unknown ID is silently dropped. Then use View Source to confirm the tag is in the served HTML, and rule out a content blocker on your own machine. See /docs/verify.

The docs have a guide for HTML, WordPress, Shopify, Next.js, React, Vue and Nuxt, Astro, SvelteKit and Remix. Anything that can serve a script tag works too. See /docs/install.

In our assessment, no. Satsu sets no cookies and keeps no persistent visitor ID: it counts visits with a daily fingerprint that changes at 00:00 UTC and can't be linked across days, so no consent banner is needed for analytics. Check with your own counsel for your site.

Pageviews, the custom events you send, outbound clicks, file downloads, scroll depth and Web Vitals. Country, browser and device class are derived on the server. The full list, including what is refused by design, is in /docs/what-we-track.

It hashes the site, IP address, user agent, the date and a daily secret into a session id. The id can't be linked across days: it changes at 00:00 UTC and the secret behind it is deleted within 48 hours. It's enough to de-duplicate visits within a day, without tracking anyone across days.

Satsu acts as a processor for your site's analytics; we provide a DPA on request. Email hello@satsu.pro.

Analytics events are stored on Hetzner servers in Finland, and are never sold or shared with advertisers.

Yes — a free tier that never expires, no card required. It includes 10,000 events a month, custom events and goals. Paid plans start at €6/mo for 500,000 events.

A pageview or a custom event you choose to track. Heartbeats that keep live-visitor counts fresh are not counted.

Events over the limit are still accepted and stored, so nothing is lost. You get an email and a dashboard banner at 80% and at 100% of the limit.

Yes. Upgrade, downgrade or cancel whenever you like. A site is never deleted because of a plan change: if a downgrade leaves you with more sites than the new plan allows, the extra sites stop tracking and keep their data until you upgrade again.

Stripe acts as Merchant of Record: it takes the payment, handles VAT and issues the receipts.

Claude Code, Cursor, VS Code and Windsurf are set up by init after it asks you. Any other MCP client gets a config to paste. See /docs/mcp.

On the free plan your agent can read visitors, pageviews, top pages and top sources within your plan's retention (3 months), and create sites, set their domain, create and edit goals. Everything else is Pro and Business: the AI channel, conversions, uptime, audits and the other actions (starting audits, creating monitors). See /docs/mcp.

Run npx satsu-analytics login. It signs you in through the browser and stores a personal key on your machine; logout removes it again. See /docs/cli.

Yes. Org API keys and the full REST API are Pro and Business; personal keys on Free reach the reduced set. The API reads analytics and, for personal keys, creates sites, goals and monitors. See /docs/api.