Everything you need to install Blipstat, read your analytics, and stay within your plan.
<script> snippet.</body>.The snippet loads blip.js from your Blipstat deployment (same host as the dashboard). That way page views are sent to /api/track on the correct origin—important when you move from localhost to production.
The script reads your tracking key from the data-key attribute. Do not remove it. One key per site; if you run multiple properties, create a site per domain.
Single Page Applications (React, Vue, etc.): include the snippet in your root HTML template so the first load is tracked. Route changes are counted when each new document load fires; in-app navigations without a full reload may need your framework’s router hooks if you want every client-side transition counted (contact support if you need SPA-specific guidance).
Your data is not reset when we deploy. Page views and sessions live in the production database. New Vercel builds only ship application code; they do not wipe analytics. What you see in the chart depends on the date range buttons (e.g. last 7 vs 30 days) and your plan's retention (older than that may be purged by a scheduled job, not by deploys).
The free tier includes a monthly view allowance and a cap on how many sites you can add (see Pricing). Usage is shown on your Account page. When you approach or exceed the limit, you’ll see warnings in the app.
Pro and Scale add REST API access, CSV export, higher request rate limits, more sites, and longer data retention. See Pricing for details.
Blipstat is built for lightweight, privacy-conscious analytics. The tracker does not use cookies for identity; it uses a short-lived session id in the browser for session metrics. Review our Privacy Policy for details you can share with your visitors and DPA needs.
data-key matches the site, and ad blockers aren’t blocking requests to /api/track.Docs are part of the app and update with your deployment. Last updated for Blipstat v1.1.