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

# PostHog

> Create an HTTP Webhook destination in PostHog's Data Pipeline pointed at your Sazabi intake URL to forward product analytics events.

[All PostHog integration capabilities](https://docs.sazabi.com/catalogs/integrations/posthog)

## About

Forward your PostHog product analytics and error events into Sazabi. PostHog's Data Pipeline posts each matching event to a Sazabi endpoint as a JSON payload, and Sazabi stores it as a log.

PostHog also has a **Connect your account** path where Sazabi provisions the webhook destination for you. See [PostHog account connection page](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/posthog.md) for that setup.

## Prerequisites

* A PostHog project with access to CDP / Data Pipeline destinations. This is a paid PostHog feature.
* The PostHog region for your project (US or EU).
* Your Sazabi intake URL (shown above).

## Set up in the dashboard

**Step 1**

### Open the destination form

In PostHog, go to **Data Pipeline > Destinations** and configure an HTTP Webhook destination.

* US PostHog: [open the webhook destination form](https://us.posthog.com/pipeline/new/hog-template-webhook)
* EU PostHog: [open the webhook destination form](https://eu.posthog.com/pipeline/new/hog-template-webhook)

**Step 2**

### Set destination values

Paste your Sazabi intake URL (shown above) into the **Destination URL** field. Set the method to `POST`, then set the body template:

```json theme={"system"}
{
  "event": "{event}",
  "person": "{person}"
}
```

**Step 3**

### Save the destination

Save the PostHog destination. PostHog starts forwarding matching events to Sazabi immediately after saving.

## Set up with the CLI

You can also register the PostHog log source with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/log-sources.md)).

Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):

```bash theme={"system"}
sazabi log-sources create posthog --mode manual
```

The command prints the intake URL for the new source — copy the whole URL and point your sender at it using the configuration shown above. Run `sazabi log-sources get <log-source-id>` at any time to reprint the endpoint, or `sazabi log-sources list` to see every log source in the project.

## Verify

Send a test event from the PostHog destination form. Open the [Intake page](https://docs.sazabi.com/guides/instrument/intake.md) in the Sazabi dashboard and confirm events from the **PostHog** source appear. Records typically arrive within a minute or two of the test event.

## Troubleshooting

**Test event delivery fails** — Confirm you pasted the full Sazabi intake URL including `https://`. Check PostHog's delivery logs for the destination to see the HTTP response code.

**No events after saving** — PostHog delivers events only when they match the destination's filter criteria. If the destination has no filter, all captured events are forwarded; if a filter is configured, verify it matches events in your recent activity.

## Further reading

> [card] [Intake](https://docs.sazabi.com/guides/instrument/intake.md)
>
> See per-source ingestion volume and health in the Intake page.

> [card] [PostHog (connect your account)](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/posthog.md)
>
> Let Sazabi provision and manage the PostHog webhook destination for you.

> [card] [Log sources](https://docs.sazabi.com/catalogs/log-sources.md)
>
> Browse the full log source catalog.


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