Why We Added Analytics: 'Did Anyone Open It?' Finally Has an Answer

You publish a quiz, a study guide, a pitch deck — and ten minutes later you're wondering if anyone looked at it. Now every host-html page comes with an answer.

The question everyone asks ten minutes after publishing

host-html does one thing: you drop an HTML file, you get a URL. For a long time, that felt complete. Publish, share, done.

Then we watched how people actually use it. A teacher publishes a quiz the night before class and sends the link to thirty students. A student turns lecture notes into a practice test and posts it in the study group chat. A freelancer ships a proposal as a polished HTML page instead of a PDF attachment.

And every single one of them, within the hour, wonders the same thing:

Did anyone open it?

A host-html page is almost never published into the void. It's published to someone — a class, a study group, a client, a team. And a page sent to someone is a message. Messages deserve read receipts.

What we shipped

Every page now has a stats view at /p/your-slug/stats, visible only to the person who published it.

On every page, free:

Total views, unique visitors, and views today
A views-per-day chart for the last 7 days

On Pro pages ($12/mo):

Top referrers: — did the traffic come from the group chat, the LMS, or somewhere unexpected?
Countries and devices: — is the class reading on phones or laptops?
Views by hour: — exactly when people opened it
90 days of history: instead of 7

No setup, no snippet to paste, no dashboard to configure. If you published the page, the analytics are already there.

Why analytics on a disposable page host?

Fair question. Most of our pages are short-lived — days, not months, on the free plan — and then they vanish; we've argued disposability is a feature. Why bother measuring something temporary?

Because short-lived pages are exactly the ones where the numbers change what you do right now:

The teacher: checks the quiz stats at 8 a.m. and sees 24 unique visitors out of 30 students. Now she knows whether to review the material or move on — before class, while it matters.
The study group organizer: sees the practice test got 11 views the night before the exam, with the hourly chart peaking at 2 a.m. The group studied. (Late, but they studied.)
The freelancer: sees the proposal was opened three times from two devices. That's a client who's circulating it — time to follow up.

A quarterly traffic report is for marketers. Per-page, same-day numbers are for people who just sent a link and need to know if it landed. That's our users.

How it works (and what we refuse to do)

We built the smallest analytics system that answers the real question, and we built it without the surveillance baggage:

No cookies.: Nothing is set in the visitor's browser.
No third-party tracking script.: Views are recorded server-side when the page loads.
No stored IP addresses.: A visitor is counted via a salted hash that includes the current date — so it can't be reversed into an identity, and it rotates every day. "Unique visitors" means unique today, not tracked forever.
Tracking can never break the page.: It's fire-and-forget; if analytics hiccups, your page loads exactly as fast as before.
Private by default.: Only the page creator — via account or edit token — can see the stats.

Your viewers are counted, not profiled. That's the whole design.

The free/Pro line, drawn honestly

We put the answer to the question in the free tier on purpose. "Did anyone open it?" is answered by views and unique visitors, and every page gets those forever, free.

Pro buys the follow-up questions: who sent them, where they were, when they read it, and how the page performed over three months. Those matter once a page is part of how you work — a tutor's course hub, a team's living report, a portfolio piece. Which is also exactly when you want pages that never expire, so the two go together.

Try it on your next page

Publish anything — a quiz, a deck, a report your agent just generated — and open /p/your-slug/stats after you share the link. The first time you watch the visitor count tick up while your class or your client is actually reading, the feature explains itself.