Skip to content
Platform · Analytics

First-party analytics that connects behaviour to conversion.

Install one snippet and read visitors, sessions, pages, events, funnels, cohorts and customer journeys from data your own site collects.

AnalyticsSample data
Visitors
9,870
+6.4%
Sessions
14,320
+8.2%
Pages / session
3.4
+0.2
Conversions
318
+4.9%
Sessions · 14 days
The problem

Sampled, third-party numbers are hard to defend.

When the numbers differ between tools, the meeting becomes an argument about data. First-party collection gives you one source you control.

Behaviour also needs to connect to outcomes: a funnel that ends at a pageview is not a funnel.

  • Numbers that disagree

    Different tools define sessions and conversions differently.

  • Behaviour without outcomes

    Traffic reports rarely link to conversion.

  • Delayed signal

    Daily exports are too slow to catch a break the same afternoon.

How it works

From snippet to insight.

  1. Add the tracking snippet

    A single asynchronous script that never blocks page rendering.

  2. Events are collected server-side

    Your site ID is validated on the server; the collector does not trust client-supplied workspace IDs.

  3. Data is organised

    Visitors, sessions, pages, events and conversions are stored in your workspace.

  4. Explore

    Funnels, cohorts, journeys and real-time signals sit on top of the same data.

Signals it reads

Behaviour
  • Visitors, sessions and pages
  • Events and properties
Outcomes
  • Conversions and definitions
  • Funnels and cohorts
Journeys
  • Multi-session paths
  • Channel transitions
What you get

Intelligence you can act on, with the evidence attached.

Intelligence produced

  • Visitor, session and page reports
  • Funnels with step conversion
  • Cohort and journey views
  • Real-time signals compared with baselines

Recommended actions

  • Find the step where the funnel loses most visitors
  • Compare cohorts before and after a release
  • Trace a converting customer’s path
  • Set an alert on a metric that must not break
Business impact

What changes for the team.

  1. One source of truth

    Everyone reads the same first-party data.

  2. Faster diagnosis

    Real-time signals flag unusual traffic or conversion changes against a same-time baseline.

  3. Behaviour tied to revenue

    Journeys and conversions sit together.

  4. Consent-aware collection

    Consent settings are enforced where leads are created from anonymous activity.

Use cases

Who reaches for it, and why.

  • Product and growth teams

    Diagnose funnels and activation.

  • Marketers

    See which pages and campaigns lead to conversion.

  • Founders

    Get a trustworthy first view of traffic without a data team.

FAQ

Questions people ask first.

Is it first-party?

Yes. Data is collected by your own workspace’s collector.

Does the script slow my site?

It loads asynchronously and queues sends, so it does not block rendering.

Can I require consent?

Yes. The snippet supports a require-consent option, and privacy settings are enforced per site.

See what is moving your numbers.

Install one tracking snippet and start reading your own data. Or ask for a walkthrough first.