PostHog is a product analytics platform that helps teams understand user behavior, measure adoption, and track important product activities. It captures events, groups, and session data across web and mobile apps. It is used by product, growth, and CS teams that want clear visibility into how users interact with their product.
Customer Success teams use PostHog to see activation patterns, usage changes, and feature engagement. It helps connect customer calls, tasks, and account decisions with real product activity so teams can act on risk, interest, and expansion signals with accurate context.
What can I do with PostHog in Custify
The PostHog integration sends events, people, and companies to Custify through webhooks. You can:
- Capture meaningful product events inside Custify
- Create Event entities linked to users and companies
- Import people and their attributes
- Import companies from PostHog group types
- Filter out noisy autocapture events
- Combine product usage with your Customer 360 view
- Connect behavior, lifecycle, and account context inside the Custify customer success platform
This integration works with incoming PostHog data. It does not pull historical activity.
How does PostHog work with Custify
Custify processes webhook payloads from PostHog and updates events, people, and companies according to your configuration.
Event processing
- Creates Event entities
- Maps distinct_id to user_id
- Uses event.uuid as deduplication_id
- Stores event properties in metadata
- Filters default PostHog autocapture events
- Allows extra filters through custom exclusions
- Links events to the correct company when group data exists
Person processing
- Maps person.id to externalIds.posthog
- Uses distinct_id as user_id
- Extracts default fields like email and name
- Builds names from first_name and last_name when needed
- Stores remaining attributes as custom fields
- Links people to all companies created from their groups
Company processing
- Creates companies from group types you configure
- Stores group.id as company_id and externalIds.posthog
- Saves group properties as company attributes
- Marks the group type on each company
- Links events and people to these companies
Batch support
- Processes arrays of events in one webhook call
- Allows partial success
- Returns a summary of processed and failed items
- Default excluded events
The integration ignores PostHog events automatically generated by browsers or apps because they create high volume activity that offers no useful customer insight. This includes navigation activity such as page views, page exits, and mobile screen views; generic interaction activity such as auto captured clicks, repeated frustration clicks, and clicks with no outcome; and system level activity such as automatic errors, app opened events, app background events, and deep link opens.
These events are excluded to keep your data clean while all custom events you track in PostHog continue to import normally as part of your Customer 360 view.
How to Activate This Integration
1. Configure the webhook inside PostHog
Set your webhook destination to:
https://your-custify-domain.com/webhook?posthogAccount=<ACCOUNT_ID>
Optional header:
x-custify-secret: <SECRET_KEY>
2. Adjust integration settings in Custify
You can configure:
- Secret key
- People import settings
- Custom excluded events
- Group types to import as companies
- Fallback linking with companyIdTrait
Save to apply your setup.
Integration Settings in Custify
You can control what PostHog sends to Custify by adjusting a few settings. People import can be enabled or disabled. Event filtering lets you add extra exclusions on top of the defaults. Group types decide which PostHog groups become companies.
Extra options such as companyIdTrait help link people to companies when no group data exists. All incoming data becomes part of your Customer 360 view.
Notes and Important Information
- Companies are created before people and events
- user_id always uses distinct_id
- People can link to multiple companies
- Events link to the first matching company
- Autocapture events are always filtered
- Batch payloads allow partial success
- Invalid items log errors without stopping processing
- The integration does not replay old events
For related automation, you can route follow ups or usage based triggers through playbooks automation.
FAQs
Does this integration import past PostHog data?
No. It processes only new events sent to the webhook.
Why did an event not appear in Custify?
It may match a default exclusion, match a custom exclusion, or fail validation. Autocapture events are always ignored.
How does Custify link events to companies?
Custify reads group data and creates companies for the group types you configure. Events attach to the first matching group.
What if a person belongs to more than one group?
Custify links the person to all companies created from their groups.
Do I need manual webhook retries?
No. Custify handles batch payloads safely. Failures do not stop processing.
How is the webhook authenticated?
Use the x-custify-secret header. Custify checks this on every incoming request.
