Help & documentation

Everything you need to install Blipstat, read your analytics, and stay within your plan.

Quick start

  1. On Sites, click Create and enter a site name and domain.
  2. Expand Get tracking code on your site card and copy the <script> snippet.
  3. Paste the snippet on every page you want to measure, ideally just before </body>.
  4. Open View analytics for that site. Data can take a minute to appear; refresh or wait for the dashboard to poll.

Installing the tracking script

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).

Dashboard & metrics

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).

  • Sites lists every property. Each has a unique tracking key and embed code.
  • Site analytics (per-site page) shows views, sessions, bounce rate, duration, top pages, referrers, browsers, and countries. Date ranges depend on your plan (from 7 days up to all-time on Scale).
  • Use the site switcher in the header to jump between properties without returning to the list.

View limits & billing

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.

Privacy & visitors

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.

Troubleshooting

No data in analytics
Confirm the embed uses the script URL from your live app (same origin as this dashboard), data-key matches the site, and ad blockers aren’t blocking requests to /api/track.
Usage not updating on Account
Usage rolls up after successful page-view ingestion. If you just fixed the embed, trigger a few page loads and check again in a minute.
Still stuck?
Email support@blipstat.io with your site name and domain—we’re happy to help.

Docs are part of the app and update with your deployment. Last updated for Blipstat v1.1.