productbet.io/Docs

PostHog

Connect PostHog to add product analytics context to your decisions and power the AI chat assistant.

Why connect PostHog?

Customer feedback tells you what people say. Analytics tells you what they actually do. Connecting PostHog gives you the quantitative side of the picture.

With PostHog connected, you can ask the AI chat assistant questions about your product usage, and ProductBet can recommend metrics when you create bets.

What PostHog provides

  • Event data - available to the Chat assistant for natural language queries
  • Usage metrics - total counts, unique users, daily averages for any event
  • Metric recommendations - when creating bets, ProductBet can suggest relevant PostHog events to measure

How to connect

Go to Settings > Integrations > PostHog and enter your PostHog personal API key and project ID. Select your region (US or EU), then click Connect.

Finding your PostHog credentials

  1. Go to your PostHog project settings at Settings > Personal API Keys
  2. Create a new personal API key (or use an existing one)
  3. When setting scopes, enable query:read (required to fetch events and stats)
  4. Copy the key (it starts with phx_)
  5. Your project ID is the number in your PostHog URL after /project/

How to use it

Once PostHog is connected, you can:

Ask questions in Chat

Go to Chat and ask analytics questions:

  • "What are our most popular events?"
  • "How many users triggered 'create_report' in the last 7 days?"
  • "Show me daily active users for the last month"
  • "What events are trending up this week?"

Measure bets

When you create a bet and define metrics, ProductBet can suggest relevant PostHog events based on the bet's context. You can also configure event mappings on the PostHog integration page to control which events map to which metrics.

Troubleshooting

  • Chat says PostHog is not connected? Make sure the integration shows as "Connected" on the integrations page. Check that your personal API key is correct.
  • No events found? Verify your project ID is correct and that the API key has the query:read scope enabled.
  • Wrong data region? Make sure you've selected the correct region (US or EU) matching your PostHog project's data residency setting.