How the community insights report works
A busy community group generates more signal than anyone has time to read. Every Monday, this reads the whole group for you and turns a week of posts, comments, and reactions into one short report: what the community talked about, who's driving it, the questions that keep coming up, and the product signals worth acting on.
A look under the hood: where the data comes from, what a week's report actually tells you, and how it stays private to the people who should see it.
The short version
It works from a complete, nightly-refreshed archive of your community group, every post, comment, reply, and reaction since the group started. Once a week it reads that archive and writes a plain-language report: engagement trends, the members driving the most activity, the themes and recurring questions, and any complaints or product signals buried in the noise. The report publishes to a private, password-protected page, so the right people can open it and nobody else can. A monthly version runs the same way on a longer window.
That's the whole job. The rest of this page is where the data comes from, what the report covers, and why it's private by default.
The data comes from a full archive, not a live scrape each time
A background job keeps a complete copy of the group in a local database, refreshed every night. The weekly report reads that archive, so it never depends on scraping the group live while you wait, and it can look at the whole history, not just the last few days. The archive is read-only to the report: the report analyzes, it never posts or changes anything in the group.
This is the part that makes real analysis possible. Trends need history to compare against, top contributors only mean something across weeks, and a recurring question is only "recurring" if you can see it repeat. A live snapshot can't do that. A maintained archive can, and it does it without hammering the group every time someone wants a number.
What a week's report actually tells you
It covers the things a community manager would want to know and rarely has time to compile: how engagement moved week over week, the members and posts driving the most activity, the themes the group is talking about, the questions that keep coming up, and any complaints or product signals worth a closer look.
The point is judgment, not a wall of charts. The numbers are pulled straight from the archive so they're accurate, and the read on top, what changed and why it matters, is written the way a good analyst would frame it in a Monday meeting. Recurring questions become a content or FAQ opportunity. A cluster of complaints about one thing becomes a product signal. A member who shows up in every top-contributor list becomes someone worth recognizing. The report surfaces those; a person decides what to do with them.
It stays private by default
The report publishes to a password-protected page, not a public URL. Only the people you give the password to can open it. The gate is structural: the page simply won't serve without the password, so a leaked link on its own reveals nothing.
This matters because a community report contains member names, what they said, and honest internal read on what's working and what isn't. That belongs to the people running the group, not the open web. Publishing it as a private page means it's easy to share with the right people and closed to everyone else, with no inbox attachment to lose track of.
Weekly and monthly, on their own schedule
The weekly report runs every Monday morning and the monthly report runs on the first, both automatically, both to their own private page. You don't trigger them and you don't assemble them. They're waiting when you start the week or the month.
For anything the standing reports don't cover, the same archive answers one-off questions directly: a specific member's history, how a campaign landed in the group, what people said about one product. The recurring reports handle the rhythm; the archive handles the ad-hoc.
This report reads and summarizes; it never posts to the group or messages a member. Community replies are a separate, human-approved workflow. This one is purely a read: it turns a week of activity into a private briefing, and a person decides what to act on.