Integrations
Connecting to PostHog
Product analytics, funnels, flags and session data, pulled into an answer or a report.
Connect PostHog through its own hosted MCP service and Gini can answer product questions from your analytics: trends, funnels, retention, feature flags, session recordings and error tracking.
What it can do
- Query trends and metrics. Whatever you would build an insight for.
- Run funnels and retention. Including the actors behind a step.
- Read insights and dashboards. What your team has already built.
- Read feature flags and experiments. Definitions, status, results.
- Read session recordings and error tracking. Including issue detail.
- Read persons and cohorts.
- Create and change things too. Insights, dashboards, flags, experiments and more, if you connect with writes.
This is the largest tool surface of any connection here by a wide margin, which is worth knowing mostly because it means the useful thing is to ask a question rather than to learn what is available.
How to connect
Open Integrations
app.ginicomputer.com → Integrations → PostHog.
Take read-only
PostHog is one of the connections where read-only is a genuinely narrower grant, and it is the right default here. Reading analytics is the job.
Sign in to PostHog
PostHog's own screen handles the authorisation.
What changes anything
| Operation | What it does | Changes anything? |
|---|---|---|
| Query trends, funnels, retention, paths | Run an analysis | No |
| Query web analytics and stickiness | Traffic and engagement | No |
| Read insights and dashboards | What your team built | No |
| Read feature flags and experiments | Definitions, status, results | No |
| Read session recordings | Including summaries | No |
| Read error tracking issues | What is breaking | No |
| Read persons and cohorts | Who is in what | No |
| Create or update an insight | Save an analysis | Yes |
| Create or update a dashboard | Change what a team sees | Yes |
| Create, update or delete a flag | Change what ships to users | Yes |
| Launch, pause or end an experiment | Change a running test | Yes |
| Delete a recording or a cohort | Remove data | Yes |
Flags change what real users get
A feature flag is not a document. Changing one changes the product for whoever it targets, immediately. If you have no specific reason to want that from chat, connect read-only and the tools are simply absent.
What it's great for
- The small questions nobody asks. "What is activation looking like this week compared to last?" Product analytics usually has a bottleneck shaped like the one person who knows the query language, and most questions never get asked because they are not worth interrupting that person for.
- Where people fall out. "Where do people drop out of onboarding, and how badly?"
- Numbers in the room. Ask in the channel where the decision is being made, and everyone sees the answer at the same time. That is different from a dashboard nobody opens.
- Checking a flag actually did something. "Is the new checkout flag moving conversion, or is it noise?"
- What is breaking. "What are the top errors this week by affected users?"
Example routine
A metric that speaks up, which is the only kind of report people keep reading:
- Every weekday morning, check activation, signups and week-one retention.
- Say nothing unless something moved more than 15% against the trailing month.
- When it did, post what moved, by how much, and the most likely segment behind it.
Good to know
- Check the window. An analytics answer is only as right as the date range behind it. Gini says what it queried, so read that line before repeating the number to anyone. See Results and sources.
- Ask for the definition when it matters. "Activation" means whatever your team defined it as. If the number surprises you, ask Gini which event it used.
- It works within your PostHog access. Projects your account cannot see stay invisible.
- Big queries cost more. A year of retention across every cohort is real compute. Scope the question when you can.
Troubleshooting
The number does not match the dashboard
Almost always a different filter, date range or event definition rather than a wrong answer. Ask Gini to show what it queried, then compare to the insight.
Gini can't see a project
Check your own PostHog access. It works with yours.
It says it cannot change a flag
You connected read-only, which is the recommended setting. Reconnect with writes if you genuinely want flags changed from chat.