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

# PostHog

> Let the Rippit agent query your PostHog product analytics alongside your conversation data.

Connect PostHog when what customers say in support conversations needs to be read against what they actually did in your product: a spike in tickets after a release, a funnel step where complainers drop off, a feature flag rolled out to the accounts that are writing in, or an error that matches a contact driver. The Rippit agent queries PostHog, reads the results, and cites them in its answer.

## What the agent gets

* **Product analytics**: trends, funnels, retention, and saved insights.
* **SQL** over your PostHog events, persons, and warehouse tables.
* **Dashboards, feature flags, and experiments**, including experiment results and flag rollout state.
* **Error tracking and session replays**, so the agent can match an error or a recording to a customer complaint.
* **Surveys, web analytics, and logs**, where your PostHog project uses them.

PostHog exposes many more tools than these, and adds to them over time. A connection picks up new tools when it reconnects, so **Manage tools** on the connection card is the authoritative list for your connection.

## Setup

In Rippit, open **Connections → MCP Servers**, choose **PostHog**, and select one of these identity options:

### PostHog personal API key

In PostHog, open **Settings → Personal API keys**, create a key with the **MCP Server** preset, and pick the project the agent should read. Paste the key into Rippit.

An API-key connection is organization-wide and acts as the PostHog user who created the key. Use a dedicated PostHog identity and keep the key's scopes as narrow as the agent needs.

### Your PostHog account

Choose OAuth to sign in to PostHog and approve Rippit. Rippit registers itself automatically, so there is no client ID or client secret to create.

An OAuth connection acts as the PostHog user who authorized it and can reach the projects that user can access.

## Regions

PostHog US Cloud and EU Cloud both use the same connection. PostHog routes to the region of the account that signs in or created the API key. Self-hosted PostHog is not supported.

## Identity and scope

Every connection uses the PostHog identity that authorized it or created its API key. If you share the connection organization-wide, everyone using the agent reads what that identity can see. Connect with an account or key whose data you are comfortable exposing that way.

## Tools

PostHog offers several hundred tools. Rippit requests the ones relevant to analyzing customer conversations: product analytics, saved insights and dashboards, SQL, persons and cohorts, feature flags, experiments, error tracking, session replays, surveys, web analytics, logs, and tracing. Tools for administering PostHog itself, such as billing, roles, data pipeline setup, and messaging workflows, are not included.

The connection starts read-only: only tools PostHog declares read-only are enabled. PostHog also offers tools that change your project, such as creating and editing insights, dashboards, feature flags, experiments, and surveys, and some of them delete data. Turn those on in **Manage tools** only if you want the agent to take those actions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.