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

# What should I track?

> To measure retention and detect churn risk, Retain needs to understand how users interact with your product. This is done by tracking the meaningful actions they perform.

## Start with a small set of events

When implementing event tracking for the first time, it’s tempting to track everything. In practice, it’s much more effective to begin with a small number of **high-value** events.

A good starting point is **3-5 events** that represent moments where users actually get value from your product.

Focus on actions that indicate meaningful product usage rather than simple page visits or passive interactions.

Events related to **onboarding and user activation are especially important**, particularly if your product offers a **free trial**, since they help identify whether users are reaching the first moments of value.

<Warning>
  Most churn happens at the beginning of the user journey, so tracking these
  early moments is critical to understand whether users are successfully getting
  started with your product.
</Warning>

**Examples might include:**

* Creating a project
* Scheduling an appointment
* Sending an invoice
* Completing a workflow
* Inviting a teammate

<Tip>
  When you create your organization in Retain, we automatically scan your
  product’s landing page and suggest a few key events based on the value your
  product provides. See the "Suggested Events" on the
  [events](https://retain.so/dashboard/events) page.
</Tip>

When naming events, keep them short and easy to understand. A simple convention that works well is: **Object + Action (past tense).**

**Examples:**

* project\_created
* appointment\_scheduled
* invoice\_sent
* teammate\_invited

## Prefer server-side tracking

We recommend sending events from your backend rather than directly from the client.

Server-side tracking is generally more reliable and secure, since it prevents exposing sensitive information such as API keys and reduces the risk of events being manipulated or sent incorrectly from the client.

It also ensures that the data being sent to Retain reflects what actually happened in your system, since events are generated directly from your application’s business logic.

## Next steps

Alright, let’s stop talking and start tracking.

<CardGroup cols={2}>
  <Card title="Installation" icon="key" href="/docs/guides/installation">
    Installing the Retain SDK
  </Card>
</CardGroup>