PostHog
Destination - Vendo sends modeled events, person properties, and group properties into PostHog using the PostHog capture and batch APIs.
What Vendo Sends
| Data | PostHog operation |
|---|---|
| Events | Capture events through PostHog’s batch endpoint |
| Person Properties | $identify calls with $set traits |
| Group Properties | $groupidentify calls with group traits |
Event Payloads
Vendo converts modeled rows into PostHog capture events.
| Vendo field | PostHog field |
|---|---|
event_name or event | Event name |
distinct_id | Person/device identity |
event_time or _timestamp | Event timestamp |
insert_id | PostHog uuid for deduplication |
properties | Event properties |
revenue, currency, order_id, platform | Added to event properties when present |
Person and Group Identity
| Flow | Identity field | Properties |
|---|---|---|
| Person properties | distinct_id | Sent as $identify with $set traits |
| Group properties | group_id or id | Sent as $groupidentify with $group_type and $group_key |
For person profiles, Vendo includes common traits such as email, name, phone, city, and country when available. For group profiles, Vendo includes common organization traits such as name, domain, and plan when available.
Platform Details
| Setting | Value |
|---|---|
| Auth Method | Project API key for writes |
| Optional Fields | Personal API key and project ID when the same PostHog app connection is also used as a source |
| Supported Hosts | US Cloud, EU Cloud, and self-hosted PostHog |
| API | PostHog /batch/ for writes and /decide/?v=3 for read-only credential validation |
| Sync Method | Server-side batch export |
| Destination Tasks | Events, person properties, group properties |
| Group Support | Yes |
Setup
- In PostHog, copy the project API key that starts with
phc_ - In Vendo, navigate to Destinations > PostHog
- Select the PostHog host: US Cloud, EU Cloud, or Self-hosted
- For self-hosted PostHog, enter the base URL of your PostHog instance
- Enter the project API key
- Select the event, person-property, and group-property tasks to export
- Save the destination and connect it to the sources or models you want to send
Verify Setup
- Trigger a test event from a connected source or run a manual export
- Confirm the event appears in PostHog’s activity feed or events table
- Check that person properties update through
$identify - If using groups, check that group properties update in PostHog
- Review Vendo integration logs for batch API errors or invalid project key messages
Troubleshooting
| Symptom | What to check |
|---|---|
| Credential validation fails | Confirm the project API key starts with phc_ and belongs to the selected host/project |
| Events are rejected | Check PostHog batch API errors in Vendo logs and confirm distinct_id is present |
| Person traits do not update | Confirm the person-property task is enabled and source rows include distinct_id |
| Group traits do not update | Confirm the group-property task is enabled and source rows include group identifiers |
| Self-hosted exports fail | Confirm the self-hosted URL is reachable by Vendo and uses the correct scheme and host |
Compatible Sources
PostHog can receive modeled events and traits from Vendo sources and models that produce event, user, or group data.
| Source | What Vendo sends |
|---|---|
| Shopify | Storefront events, order events, customer profiles, and group properties |
| WooCommerce | Order, refund, subscription, and customer events |
| Stripe | Payment, refund, subscription, and customer profile events |
| PostHog Source | Imported PostHog data routed through Vendo models or activation flows |
| Tracking SDK | First-party custom events captured through Vendo |
Last updated on