Stage 1 of 5

Fetch and Clean

Pulls raw visitor analytics, then throws most of it away.

What it does

Most analytics is not signal.

The first stage pulls the raw visitor record for the page from the PostHog API. Raw is the operative word. What comes back is every session the tracker saw, including a lot that has nothing to do with how real customers behave.

So this agent spends its time deleting things. Everything downstream reasons about what survives, which means a mistake here is the most expensive kind: the Analyst cannot tell the difference between a real pattern and a well-formed piece of noise.

Handoff

In, and out.

Each stage takes one thing and produces one thing. Nothing runs in parallel, and nothing loops back.

Receives

Raw analytics from the PostHog API

Hands off

A cleaned behavioural record, ready to reason over

Skills

What it is good at.

Data cleaning

Strips bot traffic, internal visits, and duplicate sessions before anything downstream sees them.

Cleaning

What gets thrown away.

Bot traffic
Crawlers, uptime checks, and scrapers. They scroll like nobody and convert like nobody.
Internal visits
Your own team refreshing the page they just deployed is not a customer signal.
Duplicate sessions
One person counted twice skews every rate downstream, quietly and in the wrong direction.
One runSample

1,284

Sessions fetched

231

Discarded as noise

1,053

Passed to the Analyst

Waitlist

Go touch grass.

Vivere is not open yet. Join the waitlist and we will come to you first.