PostHog analytics for every product, side by side.
Point LopeBase at your PostHog projects and see active users, pageviews, and top pages for every product on one screen.
Personal API key with read access. One-click PostHog OAuth is on the way.
What LopeBase reads
Each PostHog project becomes its own connection. Every dataset is one read-only query against that project's events.
- Web analyticsPageviews over 7 and 28 days, and weekly and monthly active people, counted across every event they sent, not just pageviews.
- Daily pageviewsPageviews and visitors for each of the last 14 days.
- Top pagesThe most viewed paths over the last 7 days, with views and visitors.
- Sources, landing pages, and devices28 days of sessions by channel, entry page, and device type, with bounce rate on landing pages and how many of each reached your goal.
- Goal eventsYour own events, like a signup or a purchase, with people in the last 28 days, the 28 before, and the last 7. PostHog's built-in events are left out.
- FunnelHow many people went through your funnel steps in order, each within 14 days, over the last 28.
- Weekly retentionGroups of people first seen in each of the last 8 weeks, and how many came back 1, 2, and 4 weeks later.
- ErrorsIf you use PostHog error tracking: exceptions and people affected in the last day, the top errors, and a daily count for two weeks.
How to connect it
- 01
In PostHog, create a personal API key with the Query read scope. The connect dialog links to the right settings page.
- 02
In LopeBase, open PostHog from Connections or the property's page and paste the key. Set the host only if you use PostHog EU or host it yourself.
- 03
LopeBase lists the projects it can see. Match each to its property, or connect All my properties from the one key.
Goal and funnel events are optional. Leave them blank and LopeBase picks a goal from the events your product already sends, preferring names that read like a signup, then a purchase, then a lead. More on linking keys to properties in Connect your tools.
What LopeBase does with it
LopeBase only runs read queries. It never changes your PostHog data or settings.
- Analytics, per propertyEach product gets a card with 7-day pageviews against the days before, a daily chart, and weekly and monthly people. See Growth analytics.
- Tracking that stoppedA site with no pageviews in the last 7 days is flagged under Needs attention. That usually means a tracking snippet broke in a deploy.
- Conversion and retention reviewLines up PostHog's sources, landing pages, funnel, and retention with Search Console and billing, and names which step to fix first.
- Errors next to SentryPostHog's own error tracking shows under Monitoring too, beside Sentry or Rollbar if you use them.
- Readable by your agentOver MCP,
read_sourcereturns every dataset above for every project. See what it can ask.
Questions it answers
Which of my products is actually growing? PostHog keeps each product in its own project. LopeBase reads them all with one key and puts them side by side, so you stop switching projects to compare last week.
Where do people drop off? Set your funnel events, like sign_up then onboarding_completed, and LopeBase counts how many reach each step in order. The retention table says whether the people who signed up last month came back.
Which channel brings people who convert? Sources and landing pages carry a converters count for your goal, so a channel with lots of visits and no signups stands out from one that sends fewer, better visitors.
Does search traffic match what Google reports? Connect Search Console to the same property and the traffic review reads search clicks next to PostHog's visitors. Add Stripe and the conversion review lines up visits with signups and payments. If a product uses Google Analytics instead, it still sits on the same Analytics page.
What it does not do, and how your data is kept
- Not a replacement for PostHogNo session replays, no feature flags, no custom insights. LopeBase reads the numbers you check every day and leaves deep analysis to PostHog.
- Fixed windowsEach dataset reads its own fixed window, 7, 14, or 28 days, so you cannot pick a date range here.
- Counts, not peopleOnly aggregates come back from PostHog: counts per page, channel, device, or event. No person profiles or emails are read.
- Never added to other toolsIf a property also runs Google Analytics or Plausible, each source shows its own numbers, since each counts differently.
- Stored safelyThe key is encrypted when saved and never shown back, to you or to an agent. See how LopeBase handles your data.
PostHog questions
Something else? Contact us.
Does this replace PostHog?
No. Keep PostHog for deep analysis. LopeBase shows the numbers you check every day, next to revenue and errors from your other tools.
Can I read projects in PostHog EU or a self-hosted PostHog?
Yes. Set the host when you connect. The US cloud is the default.
Which scope does the PostHog key need?
A personal API key with the Query read scope. LopeBase tests it with a single read query before saving.
Can one key cover several products?
Yes. One personal key can read every project you can see. Match each project to its property, and each shows up as its own source.
What if I never set a goal event?
LopeBase picks one from your events by name, like sign_up or purchase, and leaves out events that read as errors or plumbing. A goal you set always wins.
Why do PostHog's active users differ from Google Analytics?
PostHog counts people across every event they send, while GA4 and Plausible each have their own rules. LopeBase shows each source's numbers on their own so you know whose you are reading.
Put PostHog next to everything else.
Free for one property. No card.