> For the complete documentation index, see [llms.txt](https://engineering.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engineering.umh.app/engineering/development-process/how-to-decide-what-to-build/signals/product-analytics.md). # Product analytics What the usage data shows about whether a feature is doing its job. Owner: Jeremy Usage data finds problems before anyone reports them, and sizes the ones people do report. We use [PostHog](https://posthog.com/docs) for this. ## Rules * A [rollout ticket](/engineering/development-process/how-to-build/tickets/rollout.md) or a [monitoring ticket](/engineering/development-process/how-to-build/tickets/monitoring.md) can set up a [scout](https://posthog.com/docs/self-driving/scouts): it runs daily, reads the ticket, and checks its targets for adoption, impact and stability. * A scout posts only when something changed, in the ticket's own findings thread. * Evidence about a ticket that already exists goes as a comment on that ticket. A code change with no ticket yet is filed in [Triage](/engineering/development-process/how-to-decide-what-to-build/signals/triage.md). A decision for the feature's owner stays in the scout's report. * A feature's usage data lives on its [rollout ticket's dashboard](/engineering/development-process/how-to-build/tickets/rollout.md#dashboard), and the [monitoring ticket](/engineering/development-process/how-to-build/tickets/monitoring.md) reads the same dashboard after the rollout. * The [adoption target](/engineering/development-process/how-to-build/tickets/rollout.md#success) is read from that dashboard. So is the impact target, wherever telemetry can measure it. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://engineering.umh.app/engineering/development-process/how-to-decide-what-to-build/signals/product-analytics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.