> For the complete documentation index, see [llms.txt](https://docs.zellify.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zellify.app/platform-introduction/integrations/posthog.md).

# Posthog

Send funnel, quiz, and revenue data directly to your PostHog project.

<figure><img src="https://951987241-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVPontcfIF8v0iocPko5l%2Fuploads%2Fkb0Q9e2leQzTBmmpjQnu%2Feoiufthgpietbgvoejbg-5.png?alt=media&amp;token=2ebff816-7402-44aa-aa74-ade8fb2ab16d" alt=""><figcaption></figcaption></figure>

The PostHog integration allows you to track user behavior across your funnels and analyze performance inside PostHog.

Once enabled, Zellify automatically reports funnel interaction, lead capture, and payment events to PostHog, allowing you to:

* Analyze funnel progression and drop-offs
* Segment users based on quiz answers
* Build behavioral cohorts
* Track revenue and subscription performance
* Keep all product and funnel analytics in one place

If PostHog is your primary analytics tool, this integration ensures your funnel data stays fully synced.

***

### Enabling the Integration

To enable PostHog:

Dashboard → Settings → Integrations\
<https://dash.zellify.app/settings?tab=integrations>

1. Locate **PostHog**
2. Toggle the integration on
3. Enter your **PostHog Project API Key**
4. Select your **Region** (US or EU)

<figure><img src="https://951987241-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVPontcfIF8v0iocPko5l%2Fuploads%2FYkSO3sv4dTtPMqEWz9ob%2Fjoebfjoebrv-1.png?alt=media&amp;token=d478e9c0-3d33-4d2f-b8bc-5d3b2e73ee74" alt=""><figcaption></figcaption></figure>

***

### Generating Your PostHog Project API Key

To find your API key in PostHog:

1. Go to your **PostHog Dashboard**
2. Navigate to **Project Settings**
3. Locate the **Project API Key** (starts with `phc_`)
4. Copy the key
5. Paste it into Zellify

<figure><img src="https://951987241-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVPontcfIF8v0iocPko5l%2Fuploads%2FI5JaRGVP8vwaYdEUY1Xt%2Fimage.png?alt=media&amp;token=fb7f22dc-82a5-47a4-ba97-83df34602d14" alt=""><figcaption></figcaption></figure>

***

## Data Sent to PostHog

When the integration is enabled, Zellify automatically sends funnel interaction, lead capture, and payment events to PostHog.

Below is a breakdown of what data you will receive.

***

### Funnel Interaction Events

Zellify sends events as users move through your funnel, including:

* z:page\_completed
* z:email\_captured

These events allow you to:

* Track user progression between steps
* Identify drop-off points
* Analyze performance per funnel

***

### Funnel Answers

User responses are sent to PostHog in two ways.

#### On z:page\_completed

* All answers from the completed page are included as event properties
* The same answers are also stored as **PostHog person properties**

This allows you to:

* Segment users based on specific answers
* Build cohorts using quiz responses
* Analyze behavior by answer combinations

#### On z:email\_captured

* All collected funnel answers (including metadata) are included in the `answers` property

This ensures you have the full quiz context once a user becomes identified.

***

### User Identification

When the z:email\_captured event fires:

* The user’s email is set as their PostHog **distinct ID**

This ties all future events to the identified user, enabling accurate user-level analysis and cohort building.

***

### Revenue & Subscription Events

Zellify sends checkout and subscription lifecycle events, including:

* z:checkout\_presented
* z:payment\_method\_added
* z:payment\_succeeded
* z:payment\_failed
* z:trial\_started
* z:subscription\_started

These events provide full visibility into the checkout and subscription journey.

***

### Revenue Events

When z:payment\_succeeded fires:

* A **z:revenue** event is sent to PostHog

The event includes the following properties:

* revenue
* currency
* product\_id
* price\_id
* quantity
* revenue\_type
* payment\_type
* product\_name
* category

This allows you to:

* Analyze conversion rates
* Break down revenue by product
* Measure subscription performance
* Build revenue-based cohorts

***

## Automatic Tracking Features

When connected, the PostHog SDK is automatically loaded on your funnel pages.

PostHog’s default tracking features are enabled according to your project settings. These typically include:

* Autocapture (clicks, inputs, page views)
* Session recording
* Web vitals
* Page view tracking

To adjust what is captured automatically, configure these options directly in your PostHog project settings.

***

### Settings

When connecting the integration, you can configure:

* **Region** (US or EU)

Make sure the selected region matches your PostHog project region.

{% embed url="<https://jhumdfekpfmtzpbqjwsi.supabase.co/storage/v1/object/public/images/blog/1773245037315-Posthog.mp4>" %}


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zellify.app/platform-introduction/integrations/posthog.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.