PostHog

What do you like best about the product?

I like how easy it is to use with the MCP or their agent functionality. Session Replay is a game changer.

What do you dislike about the product?

I haven't really ran into any issues yet

What problems is the product solving and how is that benefiting you?

PostHog makes it super easy for us to track usage on our web app software. It really helps with understanding what users are actually doing on the platform and what issues they run into in the UX/UI.

What do you like best about the product?

A few days after we changed the onboarding flow, we noticed a drop in activation, but the main dashboard didn’t make it clear what had actually gone wrong. Traffic was still growing, signups were still coming in, and the problem wasn’t affecting every user. To dig in, we built a Funnel in Product Analytics from signup_completed to workspace_created and first_project_created, and then segmented the results by plan and device. The loss was concentrated among mobile users coming from a specific campaign. From that same funnel step, we opened the related Session Replays and watched people select an option, try to continue, and then miss the button because it stayed below the visible part of the screen. That direct link between the metric and the real user experience is where PostHog becomes especially useful for us. In other setups, I can see that conversion dropped, but then I have to copy identifiers, hunt for sessions in another platform, and hope I’m still looking at the right cohort. Here, we can go from a segment in Trends, Funnels, Retention, or Paths straight into the relevant recordings without having to rebuild the context manually. Autocapture also gives us a helpful baseline for pageviews, clicks, and form submissions before we decide which events are important enough to instrument properly.

What do you dislike about the product?

The bigger risk is that the platform makes it so easy to start collecting data that teams end up postponing key decisions around event naming, ownership, properties, and activation criteria. That approach usually works—until multiple teams are relying on the same dashboard and realize that similar events were implemented differently, or that a critical property was never captured in the first place.

What problems is the product solving and how is that benefiting you?

A redesigned onboarding experience was already live for 30% of users when the growth team noticed that first-project creation had improved, but full activation wasn’t increasing at the same pace. We opened the experiment in PostHog and compared the variants in Funnels. The new version moved more people into the dashboard, but fewer users connected the integration required to complete the workflow. Starting from the step with the biggest drop-off, we went into Session Replay and uncovered two separate issues. On smaller screens, the integration option was sitting below the fold. For other users, the copy made the integration sound optional even though the workflow depended on it. Engineering fixed the layout under the same Feature Flag, marketing rewrote the message, and product added a short Survey for users who still abandoned that stage. Before increasing the rollout, we added “connected integration” as a secondary metric and reviewed the errors tied to each variant, rather than judging the experiment only by project creation. PostHog didn’t tell us what our activation definition should be, but it did give product, growth, and engineering the same evidence. It let us improve the experience without rolling back the entire release, and it helped us expand the experiment based on a more complete view of user success instead of a single conversion number.

What do you like best about the product?

PostHog stands out because it turns raw activity into meaningful insights without feeling overly technical or overwhelming.

What do you dislike about the product?

The number of features can feel overwhelming at first, and it takes some time to learn where everything is located.

What problems is the product solving and how is that benefiting you?

PostHog helps surface insights that might otherwise go unnoticed, allowing our team to better understand member needs and improve the overall experience.

What do you like best about the product?

PostHog is one of the most useful tools for understanding what users actually do inside a product. I really like that analytics, funnels, session recordings, feature flags, experiments, surveys, and dashboards are all connected in one place, rather than being split across several different tools. The session replay feature is especially valuable because it lets us observe real user behavior, spot friction points, and better understand where and why users drop off. It also makes product and marketing decisions much easier, since we can tie user actions to clear data instead of relying on guesswork. Overall, PostHog provides a very complete view of the customer journey and helps teams iterate and improve the product faster.

What do you dislike about the product?

There is not much I strongly dislike about PostHog, but the main downside is that it can feel a little overwhelming at the beginning because it has many powerful features in one platform. Setting up events, dashboards, funnels, and feature flags properly requires some time and planning, especially for teams that are new to product analytics. Some reports could also be easier for non-technical users to understand without needing help from a developer or data person. Overall, these are not major problems, but improving onboarding, templates, and simpler explanations inside the product would make PostHog even easier to adopt.

What problems is the product solving and how is that benefiting you?

PostHog helps us solve the problem of not knowing exactly how users behave after they enter the product. Before using it, it is easy to rely on assumptions, but PostHog gives clear data through product analytics, funnels, dashboards, and session recordings. It helps us understand where users drop off, which features they actually use, and which parts of the experience need improvement. This benefits us by making product decisions faster, improving onboarding, finding bugs or friction points earlier, and measuring the impact of changes more accurately. It also reduces the need to use many separate tools because analytics, feature flags, experiments, and user feedback can all work together in one platform.

What do you like best about the product?

What I like most about PostHog is the level of visibility it gives us into real user behavior, while still staying very developer-friendly.

Session recordings, funnels, feature flags, and the event exploration tools are especially valuable. They make it straightforward to debug issues, validate experiments, and see how users interact with new features, without needing a massive analytics setup.

What do you dislike about the product?

One downside is that parts of the UI and navigation can start to feel overwhelming as you adopt more PostHog features over time.

There’s a lot of power packed into the platform, but it can sometimes take too many clicks or a bit of context switching to get to exactly what you’re looking for. Query performance on larger datasets can also occasionally feel slow or inconsistent.

What problems is the product solving and how is that benefiting you?

PostHog helps us understand how users actually interact with our product in production.

It’s especially valuable for debugging user-reported issues, validating experiments and rollouts, understanding conversion funnels, and identifying friction points in onboarding or billing flows.

The combination of analytics and session recordings in a single platform reduces the need for multiple separate tools and makes product and engineering collaboration much easier.