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

# Overview

> Track user interactions in FlagSync to measure feature impact and drive experiments.

## What Are Events?

Events log user actions—like clicks, sign-ups, or purchases—in your app.

You send them manually via the SDK’s `track()` function to capture behavior tied to features, providing raw data for metrics and experiments that help developers and product teams assess rollout effects.

## How Events Work

Call `track()` with an `eventKey` to name the event, and optionally an `eventValue` (numeric) or `properties` (key-value pairs) for extra detail:

<CodeGroup>
  ```typescript Client-side theme={null}
  client.track(
    eventKey: string,
    eventValue?: number | null,
    properties?: Record<string, any> | null
  );
  ```

  ```typescript Server-side theme={null}
  client.track(
    context: FsUserContext, // User context required
    eventKey: string,
    eventValue?: number | null,
    properties?: Record<string, any> | null
  );
  ```
</CodeGroup>

<Tip>
  Once submitted, Events appear automatically in the FlagSync dashboard—no predefinition needed.
</Tip>

* **Use Cases**: Track anything from button clicks to performance stats—whatever matters to your app.

## Events in Action

Events fuel FlagSync’s power:

<CardGroup cols={3}>
  <Card title="Real-Time Insights" icon="bolt">
    Watch them live in [Live Events](/events/live-tail).
  </Card>

  <Card title="Metrics" icon="chart-line">
    Build conversion rates or aggregates in [Metrics](/metrics/overview).
  </Card>

  <Card title="Experiments" icon="flask">
    Link them to flags in [Experiments](/experiments/overview) to test hypotheses.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="For Developers">
    Drop `track()` anywhere in your code—events auto-sync to FlagSync for analysis.
  </Card>

  <Card title="For PMs">
    Use events to spot trends or prove feature impact—no coding required to view results.
  </Card>
</CardGroup>

## Next Steps

* Start tracking with [Tracking Events](/events/tracking).
* Aggregate events in [Metrics](/metrics/overview).
* Test with flags in [Experiments](/experiments/overview).
