May 5, 2026
Most community analytics dashboards answer the wrong question.
They tell you that engagement is up 12% this month. They show you that you have 47 active members. They graph your event attendance with a nice trend line. And then they leave you exactly where they found you: with a chart, but no one to talk to.
If you're running a real community: a paid fitness collective with weekly check-ins, a women's group with sponsorship deals, a run club hosting paid events. Charts are the book cover. People are the real insights. You want to know who showed up to the last three events. Who paid for the renewal and who churned. Who used to chat every week and went quiet. The answer to every one of those questions is a list of names. And what you do next is reach out to them.
That's why we built Pulse the way we did.
The problem with the standard playbook
The default approach to analytics in community software is to give leaders the same tools a marketing team gets: dashboards, segments, metrics, exports. It looks impressive in a demo. It works fine for an annual board recap.
It fails in the moment when you actually need it. A leader reading "new members up 8%" in a dashboard does not have a path to action. She has to manually figure out who joined, build a list, copy it out, switch to her messaging tool, and start typing. By the time she's done, she's spent an hour to send a handful of messages.
We watched our most sophisticated groups operate like this. Leaders running boards, hosting paid events every week, processing tens of thousands of dollars in payments through Heylo. Pulling CSVs every Monday. Maintaining their own spreadsheets next to Heylo. Asking us for queries we couldn't run for them. The product was the bottleneck.
So we made an architectural decision: analytics shouldn't be a separate analytics product. It should be a view of your member list.
Pulse, in one sentence
Pulse shows your progress charts and the members driving them, so you can reach them in one tap.
Every chart tile (Members, Events, Chats, Payments) is a chart you can drill into. The drill-down isn't a sub-chart. It's the actual list of members the chart is counting. Tap a row, you're in their profile. Tap again, you can DM them. The path from "huh" to "done" is one screen, not a workflow.
What it actually does
Four tiles cover the questions community operators actually ask:
- Members: active right now, joined recently, paying. WAU, MAU, QAU depending on the period you're looking at.
- Events: registrations and check-ins, which events are working, who's showing up.
- Chats: message volume by channel, who's engaged, where the energy is.
- Payments: gross, refunds, by membership, event, or donation.
Compare any period to the period before it, or to the same period last year. Export any view to CSV, emailed to your admin, up to 100,000 rows, no support ticket required. Bring your whole leadership team in via the existing admin role, so the numbers aren't trapped on one person's phone.
Available on iOS, Android, and web.
Built for groups that have outgrown a chat app
If you're running a community at scale (sponsorship deals, recurring memberships, paid events that fill in 90 seconds, a board you have to report to), Pulse is the layer you've been hand-building in Google Sheets, or worse, just don't have.
This isn't more analytics. It's a dashboard where every number opens onto the people behind it. Seeing turns into reaching out, without switching apps or taking no action at all.
What's next
This is the foundation, not the finished product. Saved segments, tag-based drill-downs, more granular event analytics, programmatic exports, and group-of-groups views are on the roadmap. We'll ship them the same way: built around the people in your community, not abstracted away from them.
Pulse is included on Plus, Pro, and Business. Free groups get the Payments chart tile.