ANALYTICS

Site analytics for a page you just published

Visits, unique visitors, devices, referrers, missing pages and file downloads, counted at the edge. No tracking script to add and no cookie banner to write.

Free plan, free SSL, no credit card.

Plan availability

Which plans include site analytics

Analytics starts on Pro.

  • Free Not included
  • Starter Not included
  • Pro Included
  • Business Included
  • Enterprise Included

Read from the plan records this account is billed against, not from a page someone wrote, so it cannot disagree with what happens when you click the button. See every plan and its limits.

What it does

Counted where the bytes are served

The numbers come from the server that answered the request, not from JavaScript running in the visitor's browser.

Every request to your site passes through our edge, so that is where it is counted. You get visits and unique visitors over time, the split between desktop and mobile, which sites and searches sent people to you, which addresses returned a missing page, and how many times each downloadable file was opened. Nothing is added to your HTML, which means the numbers do not depend on the visitor allowing a script to run, and a static page you uploaded stays exactly the file you uploaded.

The download counter is the one people are usually missing. If what you published is a PDF on a link rather than a website, a page-view script would tell you nothing at all, because there is no page for it to sit in. Counting at the edge means a PDF, an image and an HTML page are all measured the same way. The missing-page list is worth the same attention for a different reason: it is usually a link you sent out with a typo in it, and it is the one report that tells you to go and fix something.

How to use it

Three steps

  1. Publish on a plan that includes it

    Analytics starts on Pro. Nothing needs to be switched on in the page itself.

  2. Send the link

    Counting begins with the first request. There is no snippet to paste and no verification step.

  3. Read it in the dashboard

    Open the site and check visits, devices, referrers, missing pages and downloads over the range you care about.

Where it earns its keep

When people reach for this

Finding out whether a client opened the preview

A build sent for review either got looked at or it did not, and that changes what the next email says. Client website preview is the workflow this sits inside.

Seeing which channel actually worked

A link goes out in a newsletter, a post and a message thread. The referrer breakdown tells you which of the three was worth the effort.

Counting downloads of a document

A price list, a menu or a resume gets opened rather than browsed. Downloads are counted per file, so a document that lives on one link still produces a number.

The alternative

Doing this without us

The usual answer is a third-party analytics script. It is a reasonable answer, and here is what it costs on a static page.

  Droply A tracking script in your page
Editing your HTML Nothing to add. The page you uploaded is the page served. A snippet in every page, re-added on every rebuild.
Blocked visitors Counted anyway; the request reached the server. Missing entirely if the script is blocked.
PDFs and other files Counted as downloads, per file. Invisible. A script needs a page to run in.
Cookie consent No cookie is set for counting. Usually a consent banner and a policy to maintain.
Page weight Unchanged. An extra third-party request on every view.

Compared against the general pattern of client-side analytics scripts rather than one named product. Checked September 2026.

When this is not the right tool

This answers "did anyone come, from where, on what". It is deliberately not a product analytics suite.

  • There are no funnels, no custom events and no per-visitor session replay. If you need those, add your own analytics script; nothing here stops you.
  • Visitors are counted without a persistent identifier, so the unique count is an estimate rather than a person count.
  • Country breakdown is not switched on yet, because it needs a geolocation database we have not shipped.
  • Numbers are for sites hosted here. We cannot report on a page that lives somewhere else, including one you copied in with site import and then took down.

Frequently asked questions

Do I need to add a tracking script?
No. Counting happens at the edge that serves your files, so there is nothing to paste into your HTML and nothing to re-add after a rebuild.
Which plan includes analytics?
It starts on Pro. Free sites are served and counted for quota purposes, but the reporting view is a paid feature.
Does this need a cookie banner?
No cookie is set in order to count a visit. You are still responsible for anything your own page loads, so if you add a third-party script yourself, that is a separate question.
Can I see who visited?
No, and that is deliberate. You get aggregate numbers: visits, uniques, device split, referrers, missing pages and download counts. There is no per-person view.
Are downloads of a PDF counted?
Yes. Files are counted individually, which is the main reason edge counting is useful here: a script in a page cannot see a PDF being opened.
Do bots inflate the numbers?
Known crawlers are classified separately so they do not sit in the same total as real visits. No classifier is perfect, so treat a small tail of odd traffic as noise.

Keep exploring