Skip to main content

PureStats documentation

Documentation

PureStats 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.js tracker, configuring privacy controls, measuring campaigns and goals, and managing your account.

Start here​

Quick startCreate a site, install the tracker, verify the first hit, and open the dashboard.Installation guidesUse PureStats with static HTML, WordPress, Next.js, React, Vue and single-page apps.Dashboard basicsUse periods, traffic modes, filters, saved segments, widgets and custom dashboards.TroubleshootingFix missing pageviews, wrong domains, blocked scripts, bot traffic and quota issues.

Common tasks​

TaskWhere to go
Add a new siteAdd a site
Confirm that tracking worksVerify installation
Track button clicks without custom codeNo-code events
Exclude private or internal pagesPath exclusions
Connect multiple domains to one siteSite aliases
Use UTM reportsCampaign analytics
Build a funnelGoals and funnels
Export a large CSVExports
Configure privacy settingsPrivacy 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 & Billing for team access, account security and usage quotas.
  • Reference for tracker attributes, JavaScript API calls, Events API payloads and troubleshooting.

Tracking at a glance​

The required client-side script is pf.js:

<script defer src="https://purestats.io/pf.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.