Analytics
First-party analytics, on your own database.
Analytics is a drop-in tracker that records what people actually do on your site — pages, events, scroll depth, rage clicks, sessions you can watch back. It is first-party: your server, your database, no third-party cookies and no broker in the middle. It also creates the visitor record every other product reads from.
Priced by tracked pageviews a month
- 100,000 pageviews / mo€90
- 500,000 pageviews / mo€240
- 2,000,000 pageviews / mo€600
How it works.
The mechanism, not the marketing. If any of this turns out not to match what the product does, the page is wrong and we want to know.
One script, one key
A single async script mints an anonymous visitor key in the browser and batches events back to your workspace. It is small, it does not block rendering, and it works on single-page apps.
Consent decides what is collected
Before consent it records only what is needed to run the page and log the consent decision. Global Privacy Control is honoured automatically, without asking twice.
Events are enriched server-side
Approximate location from IP, device, and bot and internal-traffic flags are added on our side so the browser payload stays minimal and the IP is never stored raw — only a salted hash.
Behaviour becomes an intent score
Weighted events roll into a per-visitor intent score, so you can sort by who is actually warming up rather than by who clicked most recently.
Sessions are replayable
The recorder captures the DOM, not the screen. Input fields are masked at capture — keystrokes never reach the server — and retention is a number you set.
What you get.
Session replay
Watch the real session back, scoped by consent, with inputs masked. Jump straight from a visitor in a list to the recording of what they did.
Heatmaps derived from recordings
Click and attention maps built from the sessions you already have, so there is no second script and no second dataset to reconcile.
Funnels and segments
Define a funnel over your real event types, save a segment, and get an alert when it moves.
Live map
Who is on the site right now, roughly where from, and how warm. The same map on the front of this site.
Honest attribution
First-touch and last-touch preserved on the visitor record, with "keyword not provided" said out loud for organic rather than quietly guessed.
Bot and internal filtering
Known crawlers and your own team's traffic are flagged rather than silently deleted, so you can look at humans, bots, or both.
<script async src="https://antiqore.com/embed/analytics.js"
data-embed-key="ak_live_…" data-consent-default="necessary"></script>What Analytics does not do.
Every product page on this site carries this section. It is the fastest way to be believed about the rest.
- Company identification from IP
- We do not resolve visitor IPs to company names. That practice is legally shaky in the EU and the match rates are worse than the vendors selling it admit.
- Analytics without consent
- Behavioural collection needs consent. You will see fewer visitors than a tool that ignores this. That is the trade.
- Unlimited retention
- Recordings are storage-heavy, so retention is bounded by your tier and by the number you set. Aggregates outlive the raw sessions.
Questions.
Will it slow my site down?
The tracker is async and batches its writes. It does not block rendering and it does not fetch third-party resources.
What counts as a pageview?
One page render, including client-side route changes in a single-page app. Bot traffic is excluded from the meter.
Can I self-host it?
On Enterprise, yes — inside your own perimeter, with your own retention rules.
Analytics writes to the same record as the other five.
That is the only reason buying more than one is worth anything.