PostHog community

We want to build a self-sustaining and scalable community of engaged users because it will enable us to own our audience in a way that third party social media platforms do not. Like brand or content, building a thriving community is a (very) long term bet, so we will need to both invest a lot of time up front and then wait to see what works and what doesn't.

We run several channels, and they each have a different job. For how we think about the forum, Discord, GitHub, and Reddit – and how to show up in them as a team member – read community channels.

Every one of those spaces is covered by our code of conduct. It applies to the PostHog team too.

Responsibility for community

The Builder Relations TeamBuilder Relations Team is responsible for driving our community channels and supporting community members. The Website TeamWebsite Team built the platform and tools for our online community and reviews any changes.

Support should not be considered part of community at PostHog. Support is driven by the Customer Success team, primarily using in-app support and dedicated Slack channels. Good customer support helps build positive word of mouth, but replying to support queries is not an engaging or scalable way to build a thriving community.

Content hubs

We are in the process of building these out. We have created two hubs targeting our ICP:

• Product Engineers
• Technical Founders

We have a bunch of features we are building here – more details to come!

Community forums

Our community forums live at posthog.com/forum.

The forum is our primary community channel. It used to be a public inbox of troubleshooting and support posts that were better suited to contacting us. We repositioned it with nudges toward conversational posts, a "home" layout, and better organization for discussions. Now most posts are introductions, show-and-tell, and discussions that anyone can jump into.

Anyone can still ask a question there. Support questions get routed to the right place – see community channels.

Asking a question

A user can write a question, but they'll need to create a PostHog.com account before posting. (Note: This authentication system is separate from PostHog Cloud accounts.) Users can write Markdown and upload images to a question.

Once it's posted, a question permalink page is generated, and the user is automatically subscribed to reply notifications by email.

Anyone can subscribe to thread replies by clicking the bell icon in a thread (after signing in).

Answering questions

Anyone can answer, and answering community questions covers how. It's written for community members and the PostHog team alike, and includes how we expect AI to be used and where to send questions that belong somewhere else.

If you're a PostHog user, answer with your own experience. If you think something is best answered by PostHog directly, leave it and we'll take care of it.

Some community members get a moderator role on top of that, with a small set of tools for marking solutions, tagging topics, and tidying threads. See community moderator tools for what the role can do and how we hand it out.

Points & achievements

Community members can earn achievements for activities like asking questions, helping others, voting on the roadmap, and completing their profile. Each achievement awards points that can be redeemed for stickers, merch credits, and other rewards from the Points tab on their profile.

• Points & rewards – How users earn and redeem points
• Community profiles – How to create and manage achievements