TractionScout
FeaturesWeb analytics

Cookieless web analytics that ends at sign-ups and revenue

A first-party tracker without cookies, with goals, live sessions, conversion journeys and site health, tied to the sign-ups and payments each visit led to.

Get startedTry the demo workspace

TractionScout web analytics: visitors, visits, page views, bounce rate and session time with sources and goals
Performance for the sample product Nova Launch OS, with goals and live traffic. Sample data, no account needed. Open it full screen

What you can do

  • No cookies, no stored visitor ID

    The tracker starts with consent denied, respects Do Not Track and strips sensitive query parameters like tokens and email addresses.

  • Bots stay out of your numbers

    AI crawlers, search bots, link previews, monitors and automation are recorded as bot requests, not counted as visitors.

  • Goals and conversion journeys

    Track events or pages reached as goals, attach qualified revenue, and see time and visits to convert by weekday and hour.

  • Live traffic

    Active sessions, the pages being read now, devices, locations and clients, updated as people browse.

  • Site health in the same view

    Core Web Vitals (LCP, INP, CLS), slow requests, browser and server traffic, and Cloudflare edge health sit in the overview’s health strip.

  • First-party installs

    Install with a script tag, WordPress, Next.js, Google Tag Manager, a Cloudflare Worker, NGINX, server-side events or the Go SDK.

How TractionScout web analytics works

Install the first-party tracker on your site, or send events from your server. TractionScout records page views, visits, sources and goals without cookies and without storing a visitor ID in the browser. The generated snippet starts with consent denied and respects Do Not Track, and sensitive query parameters such as tokens, email addresses and passwords are removed before anything is stored.

Three privacy modes cover different needs: standard, aggregate with consent, and EU consent required. In the restricted modes nothing is collected until your site grants analytics consent.

What you see

The Overview shows visitors, visits, page views, pages per visit, bounce rate and session time for 7, 30 or 90 days or a year. Below that are modules for where visitors come from, top pages, goals, customer journeys and retention, purchases, AI traffic and social. A collapsed data explorer lets you slice any dimension.

Goals track an event or a page reached and can carry qualified revenue. Conversion timing shows time and visits to convert, by weekday and hour. Live traffic shows active sessions, the pages being read and the devices, places and clients behind them.

Site health sits in the overview's health strip: Core Web Vitals with the thresholds Google uses, slow requests, browser and server traffic side by side, and Cloudflare edge health when connected.

Clean numbers

User agents are classified as AI crawlers, user-triggered fetchers, search bots, social previews, site monitors or automation. Those requests are kept as bot traffic and never counted as visitors, so AI crawler growth does not look like audience growth. Visits from localhost are ignored.

Installs that stay on your domain

Use a plain script tag, WordPress, Next.js, Google Tag Manager, a Cloudflare Worker, an NGINX proxy, server-side events or the Go SDK. Proxy installs keep requests on your own domain. Step-by-step instructions are in Installing web tracking.

Already using another tool?

TractionScout can also read Google Analytics 4, Plausible, Cloudflare Web Analytics, PostHog and Vercel, so you can compare figures before switching. Read Plausible, PostHog, DataFast, and TractionScout for an honest comparison.

Questions

Is TractionScout a Google Analytics alternative?

For most product sites, yes: it measures visitors, sources, pages and goals without cookies. It can also read Google Analytics 4, Plausible, Cloudflare Web Analytics, PostHog and Vercel, so you can compare before you switch.

Do I need a cookie banner?

The tracker sets no cookies and stores no visitor ID in the browser. Your site still decides when to grant consent, and in the restricted privacy modes nothing is collected until it does. Check your own legal requirements.

How is revenue attributed to a visit?

Payments sent with the trusted server key are matched to the visits that led to them. Revenue from untrusted browser calls never counts toward attribution.

Ask Scout on your own product

Which pages and sources bring visitors who actually sign up and pay?

Start with this question

Your question is carried into setup. Review it, connect the data you need, and send it to Scout when you are ready.