Files
mintlify__docs/integrations/analytics/posthog.mdx
Ethan Palm 2e99d5eab0 Clarify PostHog key safety (#6918)
* docs: clarify PostHog API key is safe to commit

Users were avoiding committing the apiKey out of caution, unaware
it's a client-side token already exposed in every browser request.

Fixes DOC-415 / mintlify/docs#609

* 💅
2026-08-07 17:37:36 -07:00

64 lines
2.1 KiB
Plaintext

---
title: "PostHog"
description: "Integrate PostHog with your Mintlify documentation site to track product analytics, feature usage, and user behavior with your API key."
keywords: ["PostHog integration", "product analytics", "feature flags", "self-hosted PostHog"]
boost: 3
---
Add the following to your `docs.json` file to send analytics to PostHog.
You only need to include `apiHost` if you are self-hosting PostHog. By default, Mintlify proxies events through `https://ph.mintlify.com` to your PostHog project.
<CodeGroup>
```json Analytics options in docs.json
"integrations": {
"posthog": {
"apiKey": "YOUR_POSTHOG_PROJECT_API_KEY",
"apiHost": "optional",
"sessionRecording": true
}
}
```
```json Example
"integrations": {
"posthog": {
"apiKey": "phc_TXdpocbYTeZVm5VJmMzHTMrCofBQu3e0kN7HGMNGTVW"
}
}
```
</CodeGroup>
## Configuration options
<ParamField path="apiKey" type="string" required>
Your PostHog project API key. Must start with `phc_`.
This key is a client-side token meant to be public. It's the same key your browser sends with every analytics event. It's safe to commit to your documentation repository.
</ParamField>
<ParamField path="apiHost" type="string">
The URL of your PostHog instance. Only required if you are self-hosting PostHog. Defaults to `https://ph.mintlify.com` (Mintlify's PostHog proxy).
</ParamField>
<ParamField path="sessionRecording" type="boolean" default="true">
Enable or disable session recording. Set to `false` to disable session recordings while keeping analytics enabled.
</ParamField>
## Session recordings
Configuring PostHog enables session recordings by default. To disable session recordings while keeping analytics enabled, set `sessionRecording` to `false` in your configuration.
```json Disable session recordings
"integrations": {
"posthog": {
"apiKey": "phc_your-key",
"sessionRecording": false
}
}
```
You need to add the URL for your docs website to PostHog's "Authorized domains for recordings" before you can receive session recordings. The option to add your URL is in PostHog's project settings.