PostHog integration
Connect your PostHog project to enrich EngageApp contacts with their acquisition UTM parameters for attribution and segmentation.
The PostHog integration pulls each contact's acquisition utm parameters into EngageApp so you can attribute contacts to the campaign or source that brought them in — and segment on it. Connecting is a one-time setup done by an owner or admin.
What it does
Once connected, EngageApp queries your PostHog project (via PostHog's HogQL query API) and enriches each contact with the UTM parameters from their acquisition — such as utm_source, utm_medium, and utm_campaign. Those become attributes you can filter and report on, so you can answer which sources produce your most engaged contacts.
Connect your project
- Open the Integrations page. Only an owner or admin can add a connection.
- Select PostHog and provide your credentials: a PostHog personal read key plus your host and project. The read key needs access to run queries against the project.
- Save. EngageApp encrypts your credentials at rest and verifies them at save time by making a test call — if the key, host, or project is wrong, the save is rejected so you catch mistakes immediately.
Use the enriched data
After the connection is verified, the pulled UTM attributes appear on your contacts. Build a dynamic segment such as "utm_source is paid_search" to target contacts by how you acquired them, or compare performance across sources in your analytics.
Manage the connection
You can review, update, or remove the PostHog connection at any time under Settings → Integrations. Rotate the read key there if it changes in PostHog; the new credentials are re-verified when you save.
Next steps
Related
Events
Send behavioral events about your contacts to trigger campaigns, gate waits, and power segments.
Contacts
How EngageApp models your end-users as contacts, the fields they carry, and the ways to add them.
Analytics
Workspace-wide and per-campaign analytics — delivered, opens, clicks, conversions, bounces, and failures.