How do I know which customers actually use what I built?

How Kicklace reads usage

Two built-in events carry the weight: activated — the first real thing somebody did in your product — always moves them to Activated, and value — the moment your product delivered what they came for — always moves them to First value, posted every time it happens rather than once. Beyond those two, Settings → Data → Pipelines names any other events of your own that count as well, up to twenty names on each rung, so "project created" or "design exported" can mean activation in your product without you renaming anything in it.

If you already run PostHog, Kicklace reads two things out of it rather than copying your whole analytics stream: a summary on every person with an address — when they were first seen, when they were last seen, and how many events they fired in the last 30 days and the last 7 — kept up to date every hour, and up to twelve event names you choose, which land on that person's own timeline as real events an automation can answer. Everything else PostHog holds is counted into those two figures and thrown away, on purpose: a product firing a million events a day is not a million rows on a timeline.

Once the facts are in, Quiet (nothing at all recorded for thirty days) and Slowing (steady or rising two weeks ago, now below steady) are populations built on exactly these signals, kept current rather than worked out fresh every time somebody asks.

Set it up

1. Post activated the first time somebody does the real thing in your product, and value every time it delivers the outcome they came for.
2. If one built-in event does not cover what activation means for you, name the rest of your own events under Settings → Data → Pipelines.
3. Or connect PostHog: Connections → PostHog → Connect, paste a personal API key, and tick up to twelve event names from what your project has already seen.
4. Press Read the history to bring in everybody PostHog already knows, then turn on its webhook destination so a named event fires an automation the moment it happens rather than waiting for the next hourly read.
5. Open People, narrow it to Quiet or Slowing, or open one person's own record to read the usage fields beside everything else they did.

What it does not do

It does not replace PostHog's own analytics — session replay, feature flags, funnels and experiments stay there. It never stores an event you did not name, not as a row and not as a copy. And nobody is put on a list because they showed up in your usage: a list needs the words a person agreed to, and PostHog does not hold them.