Skip to main content
Feedback tells you what customers say. Usage tells you what they do. Connect PostHog and Lane brings the two together in one answer: is the account asking for better exports actually exporting? Did adoption move after the release? How many active users does a request really affect?

​
What you can ask

Once PostHog is connected, ask Lane things like:
  • “How is Acme using the product? Who’s active and what do they use?”
  • “Which of the customers asking for SSO are most active?”
  • “Did usage of the new editor pick up after last week’s release?”
  • “Which people at Globex haven’t been active this month?”
Lane looks up usage per customer and per person, along with trends, funnels, retention and feature flags from your PostHog project, and answers with the feedback and customer context it already has.

​
Connect

Go to Settings → Integrations and find PostHog under Product Analytics.
  1. Choose your Region, US Cloud or EU Cloud, to match where your PostHog account lives.
  2. Choose Create a read-only key for one project in PostHog. It opens PostHog with the Read-only access preset; limit the key to the one project Lane should read, and create it.
  3. Paste the key into Personal API key in Lane and choose Connect.
Lane checks the key before saving it. It refuses project keys (the ones starting phc_), keys that can read more than one project, and keys missing permissions Lane needs, and tells you what to fix. Once connected, Lane shows the project, region and the last four characters of the key. To use a different key, Disconnect and connect again. One PostHog project per workspace. Any member except Contributors can connect it, on every plan.

​
How usage is matched to customers

Lane matches people in PostHog to your Lane customers by their exact email address and by the customer’s domain. Free email domains and your own team are never counted, so a customer’s usage reflects that customer. Keeping customer domains accurate in Lane keeps the matching accurate.

​
Where you can use it

  • In chat: ask directly, or pick PostHog from the @ menu to point Lane at it.
  • In Automations: add PostHog as a connector, for example to include usage of the accounts behind each rising Signal in a weekly brief. PostHog is always read only.

​
Privacy

  • Lane reads only. It can’t change anything in PostHog.
  • Lane asks PostHog each time it needs an answer; your PostHog data isn’t copied into Lane.
  • The key is stored encrypted and never shown again in full.

​
FAQs

Q: Why a personal API key and not a project key?
A: PostHog’s project keys are for sending events, not reading them. A personal key with the read-only preset lets Lane read without being able to change anything. Q: Can Lane read more than one project?
A: No. Lane reads one project per workspace, which is why the key must be limited to one project. Q: Why doesn’t Lane see usage for some customers?
A: Lane matches by email and domain. Check that the customer has the right domain in Lane and that the people in PostHog use their work email. Q: Can Lane change my PostHog data?
A: No. The connection is read only.