PureStats
Sign in

PureStats documentation

PureStats documentation

Learn how to set up PureStats, install the tracker, understand your analytics dashboard, manage privacy settings, and operate teams securely.

Documentation

Set up privacy-friendly analytics, verify your tracker, measure campaigns and conversions, manage teams, and keep your sites healthy.

PureStats is built for teams that want clear website analytics without turning the dashboard into a data warehouse project. This documentation covers the full workflow: creating your account, adding sites, installing the pf.min.js tracker, configuring privacy controls, measuring campaigns and goals, and managing your account.

Start here

Quick start Create a site, install the tracker, verify the first hit, and open the dashboard. Installation guides Use PureStats with static HTML, WordPress, Next.js, React, Vue and single-page apps. Dashboard basics Use periods, traffic modes, filters, saved segments, widgets and custom dashboards. Troubleshooting Fix missing pageviews, wrong domains, blocked scripts and bot traffic.

Common tasks

Task Where to go
Add a new site Add a site
Confirm that tracking works Verify installation
Track button clicks without custom code No-code events
Exclude private or internal pages Path exclusions
Connect multiple domains to one site Site aliases
Use UTM reports Campaign analytics
Build a funnel Goals and funnels
Export a large CSV Exports
Configure privacy settings Privacy Center

Product areas

PureStats documentation is organized around the main product surfaces:

  • Getting Started for account setup, installation and first dashboard use.
  • Installation Guides for framework-specific tracker placement.
  • Analytics Features for realtime, filters, campaigns, events, goals, funnels, Search Console, reports and alerts.
  • Sites & Privacy for site settings, aliases, path exclusions, retention, bot filtering and consent behavior.
  • Account & Security for team access, SSO, two-factor authentication and active sessions.
  • Reference for tracker attributes, JavaScript API calls, Events API payloads and troubleshooting.

Tracking at a glance

The required client-side script is pf.min.js:

<script defer src="https://purestats.io/pf.min.js" data-domain="example.com"></script>

Place it in the <head> of every public page you want to measure. PureStats validates the configured domain or alias before accepting events, so random hostnames and exploit-like domain strings are rejected before they enter analytics data.

Need operational visibility?

Site owners can use Site Health, verification states, scheduled reports and alert rules to detect tracking problems early.