First-party proxy analytics

Serve the tracker from your own domain when reliability matters.

PureStats supports first-party proxy setups where pf.min.js and event requests are routed through an allowed site domain.

Proxy script route included
Cached tracker included
Allowed domains included
purestats.io/analytics
PureStats analytics dashboard preview

First-Party Proxy Analytics for Better Tracking Reliability

PureStats keeps the product focused on practical web analytics: clean collection, clear reports and privacy controls that are visible before and after installation.

Reduce third-party blocking

Loading the tracker through your own domain can improve collection where third-party analytics hosts are blocked.

Cache the tracker locally

Proxy implementations can cache pf.min.js to keep page loads fast and avoid repeated remote fetches.

Keep domain controls strict

PureStats still validates allowed domains and aliases before accepting events.

Install and verify

One tracker, then setup feedback inside PureStats.

Add the script once, verify that it loads and confirm the first pageview in the site setup screen. From there, campaigns, pages, sources, devices and goals use the same reporting surface.

Tracking verification Site health status Allowed domains Privacy controls
Install snippet HTML
<script defer
  data-domain="example.com"
  src="https://purestats.io/pf.min.js">
</script>
Script found, script loads, first pageview received

Start with privacy-friendly analytics.

Create a site, add the tracker and verify the first request in minutes.

Start free beta