Open your Flarum admin dashboard and ask one question: what happened here last week? You'll get part of an answer. New registrations, new discussions, new posts — the bundled Statistics extension charts what your members did. What it can't tell you is everything that happened around them: who came to read, what they searched for, which threads they read and left without an answer, and whether the people who joined ever said a word.
This isn't a knock on Flarum — the core stays lean on purpose, and jobs like this are exactly what extensions are for. But it does mean most Flarum owners are running their communities half-blind without knowing it. So this issue is a tour of the blind spots — and how Birdseye was built to close them, one for one.
Here's what's ahead:
- What Flarum shows you out of the box
- The five blind spots
- The usual fix, and what it costs
- How Birdseye closes each gap
What Flarum shows you out of the box
Core plus the bundled Statistics extension gives you honest activity charts: users, discussions, and posts over time. That's member output — and it's worth watching.
But member output is the visible tenth of a forum. On a healthy community, readers outnumber posters many times over. Guests browse, members lurk, search engines send strangers to your three-year-old threads every single day — and none of it appears anywhere in your admin panel. View-counter extensions can stamp a raw number on each discussion, but a lifetime counter isn't analytics: it can't tell you what happened this week, or rank what deserves your attention.
The five blind spots
1. You don't know how many people actually visit. Registrations are recorded; readers are not. How many people read your forum yesterday? From where? On what? Out of the box, there is no answer — your quietest, largest audience is invisible.
2. You don't know what people searched for. Every day, members and visitors type what they want into your search box, in their own words. Flarum doesn't keep any of it. That's a content plan being written and thrown away in the same second.
3. You don't know what gets read but never answered. A thread with three hundred readers and zero replies is your community failing someone quietly. Without per-discussion view data over time, these read-to-reply gaps are structurally invisible — you'd have to catch one by accident.
4. You don't know if new members ever post. Statistics shows you the registration curve. It can't show you activation: of the people who joined this week, how many said anything within their first week? A forum can grow its member count every month while the community underneath goes quiet — and the dashboard will look great the whole way down.
5. You don't know what pulls people in. Which discussions earn steady search traffic, which sites send readers, which countries and devices they arrive on. Without sources, you're publishing into fog.
The usual fix, and what it costs
The standard answer is to paste a script tracker into the page — Google Analytics or one of its privacy-flavored cousins. Three problems:
It counts the wrong crowd. Script trackers get blocked, and forum audiences — especially technical ones — block them at far higher rates than the average web. You end up measuring whoever doesn't run an adblocker.
It costs your visitors something. A cookie banner for a tracker your members never asked for, script weight on every page, and your community's reading habits stored on someone else's servers, under someone else's retention policy.
It still doesn't speak forum. Even perfectly configured, a generic tracker gives you pages and sessions. It doesn't know what a discussion, a tag, or a member is — so search terms, unanswered threads, and activation stay invisible. You've added a cookie banner and you still have the blind spots.
How Birdseye closes each gap
Birdseye is analytics built only for Flarum, measured where a forum actually lives: on the server.
- Visitors, counted honestly. Every request is observed server-side as it happens — zero JavaScript, no cookies, nothing to consent-banner, nothing an adblocker can skip. Guests, lurkers, and the technical crowd all count.
- Search terms, kept. A card of what people typed into your search box this week. Every search that found nothing good is your next thread, handed to you.
- Read but unanswered, surfaced. Birdseye tracks discussion views over time and crosses them with replies — the read-to-reply gaps become a ranked list instead of an accident you might stumble on.
- Activation, measured. Week by week: of the members who joined, how many posted within seven days. The number that separates growth from a leaky bucket.
- Sources, countries, devices, top content. Where readers come from and what pulls them — including a world map, without a single byte of tracking script.
And the part that matters as much as the features: your stats live in your own database. Daily rollups, a few kilobytes a month, stored in your forum's DB. The processor does the math and keeps nothing. Cancel whenever you like — every stat you've collected stays yours.
The extension is free and open source, works on Flarum 1.8 and 2.x, and unkeyed it records basic daily counts entirely locally. A subscription — a flat $10 a year — unlocks the full picture, plus a weekly digest email and a permission to share the dashboard with the groups you choose. And as of 1.3.0, your forum connects the moment you save your key — no waiting a day to find out everything's working.
My honest take
Flarum's lean core is the right call — I'd rather have a fast forum and pick my own tooling than carry a bundled analytics suite most owners would never open. But "lean by design" shouldn't mean "blind by default." The questions in this issue — who's reading, what are they looking for, who's being left unanswered, do new members stick — are the ones that decide whether a community grows. You should be able to answer them without taxing your visitors to do it.
That's the whole idea behind Birdseye: the forum questions, answered server-side, with the results in your database instead of mine.
Which blind spot would you fix first? Hit reply and tell me — for my own forum it was the unanswered list, and it changed where my time goes every week.
