Connect product behavior to the decisions agents prepare.
Use PostHog data in d5s workflows to explain funnels, activation, feedback patterns, and campaign outcomes with source-linked evidence.
What agents can do with PostHog
PostHog gives agents first-party behavioral context, making it possible to test whether a reported problem appears in measured journeys. d5s keeps metric definitions, filters, and evidence visible so the resulting brief distinguishes observed movement from interpretation.
- Review approved events, funnels, and cohorts
- Compare reported feedback with product behavior
- Carry metric definitions into performance reports
Available connection methods
One public brand can have more than one verified access method. Pick the method that matches the workflow and credential policy.
MCP connection
MCP · oauth2
Query PostHog analytics, generate HogQL from questions, and manage insights.
Example compositions using PostHog
These examples show how the connector can participate in recurring work; they are patterns to build in d5s, not preinstalled workflow objects.
Customer feedback brief
Group recurring customer feedback, compare it with product behavior, and prepare a source-linked brief without overstating anecdotal evidence.
Campaign performance brief
Reconcile campaign and journey data, identify supported drivers, and draft a performance brief with explicit caveats and next actions.
Try asking
Connect PostHog to a governed workflow.
Tell us what your team repeats today. We will map the systems, approval boundaries, and first governed run with you.