![Phil J.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Phil J.") PJ Phil J. Product and Growth Lead Computer Software Mid-Market (51-1000 emp.) 7/26/2026 "A clearer way to connect experiments, sessions, and feature releases" 5/5 What do you like best about PostHog? 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. Review collected by and hosted on G2.com. What do you dislike about PostHog? 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. Review collected by and hosted on G2.com. What problems is PostHog 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. Review collected by and hosted on G2.com. Show More Current UserValidated ReviewerIncentivizedSource: G2 invite See what 1046 reviewers think of PostHog 4.5 out of 5 · Verified reviews from real users [ Read all reviews ](https://www.g2.com/products/posthog/reviews)