Documentation
Documentation
What Inqetra measures, how it gets the data, and where each answer comes from.
Inqetra measures a site from one script tag. There is no SDK to learn, no build step, and nothing to configure before it works — the tracking id is issued when you add a domain, and the snippet is live at the edge before the form closes.
What gets measured
Page views and the distinct pages people actually reached. Unique visitors. Who is on the site in the last five minutes and what they are reading. Traffic sources, grouped into Direct, Search, Social, Email and Referral at the edge. Country, browser, operating system and device. And any event you name yourself.
Every breakdown is clickable, and clicking one filters the whole view to that slice. That is the loop the product is built around: a number moved, here is the question it raises, here is the filter that begins to answer it.
Start here
- InstallOne script tag, served from Cloudflare's network. No build step, no SDK, and nothing to configure.
- Custom eventsName anything that matters and send it from the browser with one call.
- Server-side eventsFor the facts a browser must not be trusted to assert: payments, cancellations, anything a user could fake.
- What each number meansUnique visitors, page views, bounce rate, sources — defined by how they are actually computed.
- How far back you can lookNinety days is where one store ends and another begins. Which plan reaches how far, and why the boundary is there.
Worth knowing
There is no cookie banner to add, because nothing is stored that could be consented to. A visitor is a hash of their address, their browser and a salt that rotates at midnight UTC — enough to count someone once today, not enough to recognise them tomorrow. How Inqetra counts sets out the mechanism.