How to integrate Unify with PostHog
To integrate Unify with PostHog, create a Unify destination in PostHog and add the Write Key from Unify. Choose the events to forward, map Person and Company attributes, and test ingestion. Events travel from PostHog into Unify for audiences and Plays.[1]
- Connection
- Native destination
- Product analytics
- Tool
- PostHog
- Unify
- Data flow
- PostHog → Unify
- Account-specific configuration
At a glance
- Filter events before forwarding them
- Check Person and Company mappings against the real payload
- Inspect the event console before enabling the destination
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
More events do not automatically create a better handoff. Start with a behavior the team can explain, identify who or which company it belongs to, and decide what a rep should review next. Person mapping and company grouping answer different questions, so select the level of context the workflow actually needs.
A good fit when
Product and sales teams that already collect activity in PostHog and want selected events to inform follow-up in Unify.
Reconsider the plan when
If the event cannot be associated with the intended person or company, fix the mapping before designing the sales action around it.
Design the handoff
Use this framework to agree on the input, the next action, and who owns the result.
Suggested workflow design, based on the documented capabilities below.
| Stage | Decision to make |
|---|---|
| Behavior | Choose a product event and explain why it should change the next sales decision. |
| Identity | Map the relevant Person email or Company group and domain from the actual payload. |
| Qualification | Inspect the event and define the audience or Play criteria it should inform. |
| Review | Check that the receiving rep gets useful context without unsupported assumptions about the user. |
Explore the scenarios
Choose the situation that fits your team and work through the proposed plan.
Open a scenario to explore its plan. Checklists track your selections in this page only.
Build a product-usage handoff
A product team wants a useful event to inform outreach to an identified user.
Choose a specific signal and verify the Person mapping before creating follow-up rules.
- Forward the relevant custom event alongside the identification events you need
- Check that the email property maps to the intended Unify Person
- Inspect the event before using it in an audience or Play
Add account context to product activity
The team wants to understand product usage at the company level rather than as isolated user events.
A Company mapping needs the group setup and a domain. Missing company context is not fixed by forwarding more unrelated events.
- Define the company group in PostHog
- Map the Company attributes and domain
- Test the event and inspect the resulting Company context
Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.
Define success before launch
Inspect the data and the intended outcome separately. Connection status is only the first check.
Expected, not tested
The test event appears in the Unify event console with the intended Person and Company attributes.
Inspect the event and the associated records. Then validate your downstream audience or Play separately; event ingestion alone does not prove that an outbound action ran.
Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.
Questions answered
Common decisions when connecting Unify and PostHog.
Which direction does the Unify PostHog integration send data?
Selected PostHog events flow into Unify through the Unify destination. This is an inbound analytics connection, not a Unify Play sending a prospect webhook to PostHog.[1]
Can PostHog create People and Companies in Unify?
Yes. The integration can create records and fill missing attributes on existing People and Companies. Attribute mappings determine which PostHog properties supply the Unify fields.[1]
Will PostHog overwrite existing Unify data?
The guide says existing values are preserved. PostHog event data updates fields that are missing on an existing Person or Company.[1]
How do I send Company data from PostHog?
Use PostHog group analytics with a company group, map the Company attributes in the Unify destination, and make sure a domain is sent.[1]
How do I test the PostHog connection?
Use Start testing and Test function in the destination. Inspect the Unify event console and mapped records, allowing up to 5 minutes as documented, before selecting Create and enable.[1]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- Avoid duplicate collection from PostHog and the Unify Tag on the same pages
- Removing attribute mappings stops the corresponding Person or Company data from being sent
- The 5-minute visibility window is documented, not measured here
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + PostHog workflow.
Unify destination + Write Key
| Decision | What to know |
|---|---|
| Credential | Unify Write Key from the PostHog integration settings[1] |
| Event selection | Pageview, Identify, and the custom events you choose[1] |
| Person mapping | For example, email maps to {person.properties.email} when that property exists[1] |
| Company mapping | Use a company group and send a domain[1] |
| Existing data | Only missing fields are filled; existing Person and Company values are not overwritten[1] |
| Visibility timing | Test events may take up to 5 minutes to appear in the Unify event console[1] |
An attribute mapping tells the destination which PostHog property supplies a Unify attribute. Check the actual property name and type. The example {person.properties.email} is PostHog mapping syntax, not a Unify Play variable.
Technical setup reference
References and requirements for the PostHog connection.
Connection requirements and setup checklist
Before connecting
- A PostHog project already capturing the events you want to forward
- The Write Key from Settings → Integrations → PostHog in Unify
- A plan for Person and Company mappings; use a company group for company data
Create the destination
In PostHog, open Data → Destinations → Create a new destination. Search for Unify and choose Create.[1]
Select the events
Add an event matcher for the events you want to forward. The guide recommends Pageview and Identify events alongside relevant custom events.[1]
Map the attributes
Paste the Unify Write Key and review the Person and Company mappings against your actual PostHog properties. For Company data, configure a company group and send a domain.[1]
Test before enabling
Select Start testing and Test function. Check the Unify event console; the guide allows up to 5 minutes for events to appear. After confirming the data, select Create and enable.[1]
Troubleshooting
Start with the stage where the expected data or action stops appearing.
An attribute arrives empty
Compare the mapping path with the actual PostHog payload. A property named email_address needs the matching path rather than a mapping to email.[1]
Company data is absent
Check that a company group exists, its attributes are mapped, and a domain is sent.[1]
Events are counted twice
The guide warns against running the Unify Tag on the same pages as PostHog. Audit the collection paths before enabling both.[1]
Sources & review
Official documentation reviewed on September 15, 2026.
Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.
Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.
Content updated: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
