> For the complete documentation index, see [llms.txt](https://uci.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uci.sunbird.org/use/adopter/posthog-event.md).

# Posthog Event

## Overview

PostHog is the all-in-one product analytics suite. PostHog provides everything product-led teams need in one place, including:

* Product Analytics
* Aggregate Dashboard
* Insights
* User lifecycle
* Event pipelines
* Export data

In UCI we are also using PostHog for creating aggregate dashboard by sending the events on each conversation. The events follow given [specification](https://github.com/sunbird-specs/Telemetry/blob/master/learn/specification.md).<br>

## Steps to use PostHog events

### 1. Create Posthog Account

First we would need to create a new account on [Posthog](https://app.posthog.com/signup) & get a project api key. The project api key will be available in [Project Settings](https://app.posthog.com/project/settings) of Posthog account.

### 2. Enable Posthog Event in UCI

To enable posthog events in UCI follow below steps.

1. Add below environment variables for posthog url & api key. [Link to environments of UCI](/use/developer/development-environment.md).<br>

   ```
       POSTHOG_TELEMETRY_APIKEY= // Api key
       POSTHOG_TELEMETRY_URL=https://app.posthog.com
   ```
2. Add environment to enable posthog event.<br>

   ```
       POSTHOG_EVENT_ENABLED=TRUE
   ```
3. After the posthog events are enabled, UCI will send all conversations as events to posthog. we can generate aggregate dashboard with these events using insights, actions etc.&#x20;

### 3. Create insights in Posthog&#x20;

We can create insights like counts, graphs etc using posthog insights. Use this [documentation](https://posthog.com/docs) to better understand the insights, funnels, life-cycle etc that posthog provides.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://uci.sunbird.org/use/adopter/posthog-event.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.