Documentation

Install Statsdot, configure the script, track events and goals, and use the REST API and the MCP server.

• Get started in three steps Account, site, snippet: your first numbers in five minutes.
• Installation guides Every platform with its step-by-step guide.
• WordPress and WooCommerce plugin Install, settings and WooCommerce events.
• Script configuration data-domain, data-auto, single page apps, localhost and what the script sends.
• Exclude your own visits One line in the browser console, and no snippet outside production.
• Subdomains and several sites Each domain or subdomain is a site; www is the same site.
• Serve the script from your own domain Nginx, Cloudflare Workers, Next.js and Netlify proxies.
• Import your history from Plausible Upload Plausible's CSV export to keep your history.
• Events and goals Events with or without code, labels, automatic links and downloads, and goals.
• Campaigns and UTM tags utm_source, utm_medium and utm_campaign, as stored by Statsdot.
• Filters and date ranges Click any row to filter; ranges, custom periods and pinned periods.
• Notes, main goal and alerts Chart notes, the #1 KPI and email alerts.
• AI crawler tracking Turn it on, then connect WordPress, Laravel, PHP, Node or Next.js.
• Funnels Ordered steps within a day, drop-off per step.
• Measure scroll depth An optional second script that shows how far down each page people read.
• Invite your team Viewers, managers, invitations and plan limits.
• Shared dashboards A private link to one site's dashboard, read only.
• Live visitors widget A badge or card with the visitors of the last five minutes.
• Weekly report by email Monday emails with last week's visitors, pages and sources.
• Privacy and cookieless counting The daily visitor code, what is stored, retention and consent.
• REST API Authentication, endpoints, ranges, filters, errors and limits of the Statsdot API.
• Connect an AI assistant (MCP) Set up the Statsdot MCP server in Claude, ChatGPT, Claude Code, Cursor and Codex, and the tools it offers.
• Apps built on the API What already uses the Statsdot API, and ideas to build on it.
• No data in the dashboard Domain, caching, consent tools, ad blockers and local testing.
• Content Security Policy The two directives to add.
• Plans, events and limits Events, tiers, trial, site and team limits.