Every analytics tool tells you what changed.This one tells you what to ask.
Inqetra compares each period against the one before it, finds the moves large enough to be real, and hands each one back as the question you’d have to answer next — with the filter already attached.
- Free tier
- One site, 30 days of history, no card.
- Install
- One line, under 1.5KB gzipped, no build step.
- Privacy
- No cookies. No visitor recognisable the next day.
A working Inqetra overview
inqetra.com
Last 14 days, by day
Now plotting Unique visitors: 12,480 visitors, last 14 days, by day. 3 questions worth asking, beginning “Where did the new visitors come from?”.
This periodPrevious
Worth asking
- Where did the new visitors come from?Encouraging: Referral, up 41%
- Did they reach more than one page?Concerning: Pages per visit fell 3.1 → 1.4
- Which referrer sent them?Encouraging: news.ycombinator.com
Illustrative figures from a demonstration site. Every interaction here is the one the product ships.
Pick a metric above and the chart re-plots against the same window a fortnight earlier.
The questions change with it — the same gesture the product performs on a Monday morning.
Installed in about a minute
There is no SDK to learn and no cookie policy to write, because there is nothing stored to consent to.
- Add your domain
- One field. Inqetra issues a tracking id and publishes it to the edge before the form closes, so the snippet works immediately.
- Paste one line
- Under 1.5KB gzipped, served from Cloudflare’s network. No build step, no SDK, and nothing to design a consent banner around.
- Read what it asks
- Once there is a period to compare against, the inquiry rail starts naming what moved and hands you the filter that begins to explain it.
<!-- Inqetra -->
<script defer src="https://collect.inqetra.com/inqetra.js" data-site="9f1c4b2e-7a30-4d51-b8c6-2e5a0d7f3c11"></script>Paste it just before the closing </head> tag.
Everything the questions are drawn from
Each of these is a breakdown you can click. Clicking one filters the whole view to that slice, which is how a question becomes an answer.
- Page views and total pages
- Every view counted, plus how many distinct pages people actually reached — the number that tells you whether a site is being explored or bounced through.
- Sources, grouped by channel
- Social, Search, Email, Referral and Direct, classified at the edge. Six networks at 3% each stop looking like noise the moment they add up to 18%.
- Active users, live
- Who is on the site in the last five minutes and what they’re reading, refreshed continuously — alongside the unique-visitor total for the whole period.
- Custom events
- Payments, cancellations, upgrades, searches. One call from the browser, or an authenticated call from your backend for the things a browser must not be trusted to assert.
- Server-side API keys
- Scoped per site, hashed at rest, revocable in a click, and rate limited at the edge. The plaintext is shown exactly once.
- Geography and technology
- Countries, browsers, operating systems and devices — each one clickable, each one pivoting the whole view to that slice.
Priced by how far back you look
The tiers follow the storage rather than inventing a boundary. Ninety days is where Analytics Engine ends; past that, queries run as unsampled SQL over an Iceberg table in R2, which is slower and billed by the byte. Only the top plan buys that.
Free
One site, the last 30 days, no card.
$0forever
- 1 tracked site
- 30 days of history
- Unlimited page views — ingest is never throttled
- Full breakdowns, channels and the inquiry rail
Pro
The whole hot window, and the AI read of it.
$9per month
14-day trial. The card is charged when it ends, not before.
- 5 tracked sites
- 90 days of history — the full Analytics Engine window
- AI reads: what moved, and what to look at first
- 3 server-side API keys for events a browser cannot assert
- Unlimited page views, still
Scale
A year of history, and every property you run.
$29per month
14-day trial. The card is charged when it ends, not before.
- 12 months of history, read from the R2 lake rather than sampled
- Unlimited tracked sites
- Unlimited server-side API keys
- Everything in Pro
Ingest is never throttled on any plan — a traffic spike is not a reason to stop counting. What the plans differ on is how far back you can look, how many properties you can hold, and whether the AI read and the server-side event API are available.
Why the numbers can be trusted
Analytics is easy to get confidently wrong. Three decisions in the architecture exist to make that impossible rather than unlikely.
Workers at the edge
Ingest runs in the colo nearest the visitor. Identity is derived there from a daily-rotating hash, so the raw address never travels and never lands.
Analytics Engine, then R2
The last 90 days answer from Analytics Engine in milliseconds. Anything older is read from an Iceberg table in R2 over R2 SQL — exact and unsampled, out to twelve months.
KV on the hot path
Site lookup and visitor dedup resolve from KV, never from the tenant database. The collector has no D1 binding at all, so a traffic spike on your site has no route to reach it.
Questions worth asking first
The ones that decide whether this is worth installing, answered with the mechanism rather than a reassurance.
Do I need a cookie banner?
No. Inqetra sets no cookies and stores no addresses. A visitor is identified by 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 is this different from a dashboard full of charts?
Every dashboard can tell you a number moved. Inqetra compares each period against the one before it, finds the moves large enough to be real, and returns them as questions with the filter already attached — so the next click is a step towards an answer rather than a guess.
What counts as a custom event?
Anything you name: payment, subscription_cancelled, trial_started, docs_search. Fire it from the browser with window.inqetra(), or from your backend with an API key when the event asserts something the browser shouldn’t be trusted with.
What happens past 90 days?
Every event is also streamed into an Iceberg table in R2 as it arrives. Analytics Engine answers the recent windows quickly and cheaply; anything reaching further back is answered from the lake with real COUNT(DISTINCT), unsampled.
Will it slow my site down?
The snippet is under 1.5KB gzipped, loads deferred, and sends events with sendBeacon so nothing blocks navigation. It is served from Cloudflare’s network, and it is written so that any failure inside it is swallowed rather than thrown into your page.
Is there a trial, and when does the card get charged?
Pro and Scale both start with 14 days. The card is authorised at checkout and charged when the trial ends, not before, and cancelling inside the window means it is never charged at all. Free needs no card in the first place.
What happens if I hit the site limit?
Adding another property is refused with the plan that would allow it named in the message. Nothing already collected is deleted and nothing stops being counted — ingest is never throttled on any plan, including Free.
Can I cancel, and what happens to my data?
Cancel whenever you like, from the billing portal. Every paid feature keeps working to the end of the period you have already paid for, then the account moves to Free. Nothing that has been collected is deleted; the shorter window only limits how far back you can query.