---
title: PostHog
slug: posthog
docTags: 
createdAt: 2025-06-02T18:47:15.780Z
---

# Introduction

PostHog is an open-source product analytics platform that helps teams understand how users interact with their web or mobile apps. It combines event tracking, session replays, heatmaps, feature flags, and A/B testing into a single platform—allowing product and engineering teams to analyze behavior, test features, and ship improvements faster.

Unlike many analytics tools, PostHog can be self-hosted, giving teams full control over their data and compliance. It’s especially popular with teams that want powerful analytics without sending data to third-party servers.

# Getting started

You need your Project API Key to connect to this destination. You can find your Project API Key under [Project Settings](https://app.posthog.com/project/settings) in PostHog.

# Connecting to the PostHog CDP destination

1. Log into the Chord data platform.
2. Navigate to the CDP.
3. Click the **"Add" **button next to Destinations.
4. Select **PostHog **from the destination catalog.
5. Enter in the destination name and the **PostHog Project API Key**. 
6. Click **"Create" **to connect.

# Chord events relevant for destination

Not all Chord Tracking events are used downstream in your configured destinations. The most relevant and important events in the Chord tracking plan are mapped within the CDP destination, relayed and then ingested in the destination. The Chord tracking plan events used by the the [Posthog](https://posthog.com/docs/data/events) destination are: 

| **Chord Tracking Event** | *Destination Event*                       |
| ------------------------ | ----------------------------------------- |
| **Identify**             | *No event specified, user identification* |
| **Page**                 | *pageview*                                |
| **All Track Events**     | *Event name passed as is*                 |



:::hint{type="danger"}
Before connecting destinations in the Chord CDP, please verify with all Destination owners that all **non-Chord CDP** configured destinations are *disabled.*
**
Running external destinations alongside configured Chord CDP destinations ***can result in duplicate events downstream. ***
:::