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 product analytics, investigate errors, and manage insights, experiments, feature flags, and CDP workflows.
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.
See the workflow
Campaign performance brief
Reconcile campaign and journey data, identify supported drivers, and draft a performance brief with explicit caveats and next actions.
See the workflowContent performance brief
Read product and search analytics for the published set, separate genuine movement from normal variance, and prepare a brief that names what to write more of.
See the workflowTry asking
Connect PostHog to a governed workflow.
Each one arrives with a persona, standing instructions, a wake-up schedule, and its connectors chosen. Nothing runs until you add it.