Direct data source
Connect customer feedback to PostHog behavior
PostHog shows what customers did. Calls, tickets, and messages explain why. Poth connects product analytics to qualitative evidence so behavioral patterns can be investigated instead of merely observed.
What Poth reads from PostHog
Poth supports PostHog as a direct product-analytics source. A company admin configures the project or environment and permissions. HogQL imports provide bounded preview rows; a durable full-corpus ingestion path requires a configured PostHog Batch Export destination.
Coverage boundary: HogQL imports are preview-only. Without a configured Batch Export destination, the source must not be described as a complete PostHog corpus. Imported records also remain bounded by the selected project, permissions, export window, and delivery settings.
Questions you can investigate
- Why do accounts that start onboarding fail to activate?
- What did customers say before their product usage dropped?
- Which requests come from accounts that use a feature most heavily?
- Do support complaints line up with a measurable behavior change?
These are example questions, not claims about a customer result.
Connect what customers say to what they do
Behavior alone does not establish a cause, and feedback alone does not show how widespread a problem is. Poth joins PostHog context to authorized calls, support, CRM, billing, and other evidence while preserving source provenance for the resulting analysis.
How the connection works
A company admin supplies the PostHog host, project or environment details, and a personal API key. That connection can return bounded preview data. Full-corpus ingestion requires a PostHog Batch Export destination configured for the Poth source.
Poth preserves source identity so an answer can expose its cited evidence, retrieval context, and uncertainty instead of flattening the source into an unattributed summary.
Related integrations
Ask the question across your own data
Connect a supported source, then inspect the cited evidence and retrieval context behind Poth's answer.