PostHog
Vendo imports product analytics data from PostHog for unified reporting, identity analysis, and downstream activation.
Last reviewed September 22, 2026
Source: Vendo reads product analytics data from your PostHog project, including events, persons, groups, and session recording metadata.
Sync Coverage
| Data | Description |
|---|---|
| Events | Product and analytics events from the PostHog Events API |
| Persons | Identified user profiles and person properties |
| Groups | Account or workspace-level group profiles |
| Session recordings | Session recording metadata; recording blobs are intentionally skipped |
Setup
- In PostHog, create a personal API key with read access to the target project.
- Copy the PostHog project ID from your project settings or project URL.
- Confirm whether the project is hosted in US Cloud, EU Cloud, or a self-hosted PostHog instance.
- In Vendo, add PostHog as a source.
- Enter the personal API key, project ID, and host setting.
- Save the source and run the initial import.
Credentials and Configuration
| Field | Required | Description |
|---|---|---|
personal_api_key | Yes | PostHog personal API key used as the bearer token for API reads |
project_id | Yes | Numeric PostHog project ID |
host | Yes | us, eu, or self_hosted; defaults to US Cloud when omitted |
self_hosted_url | When self-hosted | Base URL for your PostHog instance, such as https://posthog.example.com |
Verify Setup
- Confirm the PostHog source shows an active status in Vendo.
- Check that event rows are arriving in the PostHog events table.
- Confirm persons and groups appear when those resources exist in PostHog.
- Re-run a recent time window and confirm event counts stay stable instead of duplicating.
Operating Notes
- Events and session recording metadata are time-series resources.
- Persons and groups are snapshot resources.
- Vendo stores session recording metadata only. It does not copy playback blobs.
- Self-hosted projects must provide a valid HTTPS
self_hosted_url.
Last updated on