Analytics

Every number your site makes. Including the ones AI made.

One line on your site. Visitors, sources, goals and funnels — and the assistants reading your pages to answer somebody.

Start with 10k events for $5Try the dashboard

348AI reads on our own site in 28 days3.9 KBgzipped tag, no build step$5for 10k events a month

Events on pages Quillly hosts never count · Cancel anytime

Watch

The whole dashboard in 40 seconds

What the film shows, in order:

  1. Analytics, by Quillly.
  2. Step 1, sources. Where do your visitors come from? Every source, AI chats too: channels, sources and landing pages, with AI chats on their own row. Example data.
  3. Step 2, AI reads. Which assistants read your pages? Count the readers who never visit: assistants fetching a page to answer someone, on the pages Quillly serves. No tag can see these. 348 AI reads on quillly.com in 28 days, 98.6% of them ChatGPT.
  4. Step 3, page insights. Where do readers stop? See where readers stop: a score from how people read each page, and every problem comes with its fix. In the example, 52% of readers who reach “Pricing compared” stop there.
  5. Step 4, goals. Which visits turn into sales? Name what counts: put a goal on the button that matters, and it creates itself the first time it fires. The funnel shows the drop on every step. Example data.
  6. Quillly Analytics. Every number your site makes. Start collecting: one line on your site, cancel anytime.
Analytics · Overview
The Quillly analytics overview for a demo site: visitors, AI answers, search clicks, search impressions, bounce rate, session time and a live online count above a daily traffic chart, with a tooltip open on one day showing its page views, pages per visitor, and its split of new and returning visitors.
Every point on the chart names its own numbers — this is the real dashboard, not a drawing of it.

The overview of a demo site: visitors, AI answers, search clicks and impressions, bounce and time on page above one chart. Every point names its own numbers.

How it works

Live in three steps.

  1. 1 Paste one line

    3.9 KB gzipped, async, no build step. The install card turns green when the first visit lands.

  2. 2 Name what counts

    Put a goal on the button that matters. It creates itself the first time it fires.

  3. 3 See what brought them

    Channels, sources and the pages people land on. Example data.

Page insights

See where readers stop, and what to change.

Every page with the tag gets a score from how people read it: how far they get, what they click, whether they move on. Each problem comes with its fix.

Page insightsHow to choose an AI blog writer in 2026
Pictured 2 days ago
57Room to improve ↗ +852% of readers who reach “Pricing compared” stop there.412 visitors since the page changed on Sep 3
Judged byRead to the end22% of visitors · target 50%
What to improve
  • 52% of readers who reach “Pricing compared” stop there.Shorten this section, move its main point to the top, or break it up with a list, a table or a picture.
  • Visitors click “Compare plans →” again and again.Check that it works and answers within a second, on a phone too.
  • People click “Cost per post” and nothing happens.Make it a link or a button, or stop styling it like one.
  • Phone readers reach the end less often (14% against 31% on desktop).Open the page on a phone and check wide tables, large pictures, pop-ups and sticky bars that cover the text.

Example data. In the dashboard it is drawn over a full-length picture of your own page.

  • No score before 30 visitorsUntil then the badge counts up: 12/30.
  • One vote per visitor a dayFifty visits from one person count once. Your own browser can be left out.
  • Starts over when the page changesA new or renamed section starts fresh, with the old score beside it.
  • Off your event meter3.4 KB, fetched when the browser is idle. Reports never count as events.
  • No recordingsNo replay, no mouse trails, nothing typed into a field.
A score in every list

An Engagement column beside SEO in your content tables and site pages. Click one to open its page.

Readers, in the editor

Your outline shows how many readers reach each section while you rewrite it.

Your agent reads it too

The same score, sections and fixes over MCP, so it can rewrite the part that loses people.

AI reads

Count the readers who never visit.

An assistant fetching your page to answer a question is not a crawl and not a session. It is counted only when its operator says so in writing.

348AI reads on quillly.com
in 28 days
  1. An assistant fetches the pageRead from the User-Agent on the server — assistants run no JavaScript, so no tag can see one.
  2. Its operator says why, in writingWhen users ask ChatGPT or a CustomGPT a question, it may visit a web pagedevelopers.openai.com/api/docs/bots · read 30 Aug 2026
  3. On the pages Quillly servesA site that only pastes the tag sees zero here. That zero means we cannot see, not that nobody is reading.
In the dashboard

The numbers a small team actually opens.

Your own visits, left out

Stop counting the browser you check from, per site address. No IP rules, so colleagues still count.

Speed from real visits

Core Web Vitals at p75 from your own pages, and the five slowest.

One visitor's trail

Where they came from, every page on the way, and the goal it ended in.

Search, beside your traffic

Clicks, impressions and positions from the engines you connect. Never added to visits.

Countries and devices

Country, browser, system and device for every visit. Country is as far down as it goes.

Privacy you choose per site

The default tag sets one first-party cookie; the cookieless one writes nothing.

Every figure in these tiles is example data.

Works with

Anywhere you can paste a script tag.

The same line in your framework's layout or your builder's custom-code box. Some builders only open that box on paid plans.

Code
  • Next.js
  • React
  • Vue
  • Astro
  • Nuxt
  • SvelteKit
  • Laravel
  • Django
Site builders
  • WordPress
  • Webflow
  • Framer
  • Shopify
  • Ghost
  • Wix
  • Squarespace
  • Carrd

Pages Quillly hosts need nothing. The tag is already on them, and their events never count toward your plan.

Agent access

Ask your agent, not the dashboard.

Claude, ChatGPT, Cursor and the rest read every number the dashboard draws, and set up goals and funnels for you, over MCP.

quillly.com's own numbers, 28 days

What did AI assistants read on my site in the last 28 days?

get_website_analytics · range 28d

348 reads on quillly.com — ChatGPT 343, Claude 5. The most read was your AI search statistics post, read 135 times.

Add a goal for signups.

manage_analytics_goal · create "signup"

Done. Put data-qa-goal="signup" on the button and it counts from the next click.

Connect your AI
Pricing

Priced by events, not seats.

Four sizes, every website you own, 2 months free on the year.

Events per month
Analytics 100k$12/monthor $120/year — $10.00/mo billed yearly
Start collecting

Events on pages Quillly hosts for you never count.

Every size includes
  • 100k events a month
  • Unlimited websites
  • Goals, funnels & journeys
  • AI-answer and crawler traffic
  • Search Console & Bing connected
  • 90-day retention
Questions

Before you install.

Still deciding?Write to [email protected]. A person answers, usually the same day.Contact us
What counts as an event?
Every stored row: a page view, a time-on-page, a web-vitals beacon, a scroll milestone, a goal, an identify. It is pooled across all your websites and resets on your own billing anniversary — 10k of them on the entry tier. Events from pages Quillly serves for you are never counted at all.
What happens when I hit the limit?
Collection pauses for the rest of the period and nothing is billed — no overage charge, no auto-upgrade. The endpoint still answers normally, so your pages never log a failed request because of our billing state. An email at 80%, another at 100%, and a banner naming the reset date. The gap in the data is real and permanent; upgrading resumes collection immediately.
Does it set a cookie?
The default tag does: one first-party cookie, thirteen months, so returning visitors are exact. The cookieless variant writes nothing to the device and derives an id from a salt that rotates at UTC midnight — what you give up is that a visitor who returns tomorrow counts as new. It is a per-site switch and changing it never gaps collection. In the EU or the UK, assume the default needs a consent banner; that is your call for your site and we will not tell you otherwise to win a comparison.
Will it slow my site down?
The default tag is 3.9 KB gzipped, loads async, never blocks rendering, injects no DOM node and reads no layout. Once the browser is idle it fetches the page-insights module (3.4 KB, cached for a year), which checks where your headings sit a few times per visit, never on every scroll, to measure how far visitors get; it writes nothing to the page either. Events batch and flush about 700 ms later, and the last flush rides sendBeacon on pagehide. Every capability is feature-detected, so an old browser degrades quietly instead of throwing inside your page.
How is a page's engagement score worked out?
From how far visitors read, how long they pay attention, what they click and whether they do what the page is for: finish an article, move on from any other page, or a goal you pick. There is no score until 30 visitors have seen the current version, each visitor counts once a day, and nothing is recorded: no replay, no mouse trails, nothing typed.
Why can you see AI assistants when other analytics cannot?
Because assistants do not run JavaScript, so no client-side tag can ever see one. They are read from the User-Agent on the server, which means we have to be serving the page — so AI reads exist for content Quillly hosts or proxies for you, and a site that only pastes the tag sees zero there. That zero means we cannot see, not that nobody is reading you. An assistant enters the number only when its operator publishes a user-agent list saying it fetches because a user asked, and we store the document URL beside it.
How is it different from GA4, Plausible or Fathom?
No sampling, a session you can explain in one sentence, and one page of fixed cards. Against GA4 you lose segments, cohorts, attribution modelling and BigQuery. Against Plausible and Fathom you gain AI reads, free analytics on pages we host, agent access, and a lower price — our 10k tier is $5. Where they are ahead: retention of years against our 90 days, and a raw data export. If either is your requirement, say so before you buy.
Can I get my data out?
An AI agent can read every number the dashboard draws through MCP, and the keyword explorer exports the rows you are looking at as CSV. There is no raw event export, no API that pages the raw stream and no warehouse drop. If that is a requirement, it does not exist yet.
How long is data kept?
Ninety days for events, sessions, visitors and crawler hits — every plan, no exceptions, enforced by a database expiry rather than a job. Two things outlive it on purpose: your goal counters, so all-time totals stay true, and anyone you have identified, because a person who has not visited for 90 days is still your customer.
Do I need the rest of Quillly?
No. The Analytics plan is analytics and as many websites as you want to connect. Content publishing, the SEO tools, the agent and directory listings are separate lines you can add later, and the dashboard does not show menus you have not bought.

See who reads your site.

One line on your site, and every visit — human or AI — is counted from today.

Start collecting See the sizes

From $5 a month · Cancel anytime