> ## Documentation Index
> Fetch the complete documentation index at: https://docs.woes.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Update Analytics

> Measure widget update impressions, clicks, and follow-up support impact.

# Update Analytics

Update analytics answer one question: did the update help customers understand
or act?

## What Woes Tracks

| Signal                | What it tells you                                                          |
| --------------------- | -------------------------------------------------------------------------- |
| Impressions           | How often the update was shown in the widget Updates tab.                  |
| CTA clicks            | Whether customers followed the linked docs, release note, or product page. |
| Related conversations | Whether customers still ask about the same topic after publication.        |
| Related issues        | Whether the update reduced or exposed follow-up support work.              |
| Survey results        | Whether customers report that the follow-up was useful.                    |

Widget update metrics come from widget events. They are directional product
support signals, not email-delivery receipts or Discord announcement metrics.

## Review Workflow

1. Compare related conversation volume before and after the update.
2. Review customer replies for unresolved confusion.
3. Check whether linked docs or product context need another update.
4. Tag follow-up issues consistently.
5. Add findings to the product or support review.

## Better Follow-Ups

If an update creates confusion, publish a smaller, clearer follow-up rather than
a broader announcement. Focus on what customers need to do next.