Sold by
PostHog
PostHog aims to equip every developer to build successful products.We do this by providing the tools teams need to capture events, analyze data, record user sessions, conduct experiments, deploy new features, track errors, run surveys, provision data warehouses, observe LLM-powered features, and more.By offering all of these tools in one platform, PostHog replaces a entire stack of point tools with a single, fast-moving product. Plus, we're shipping new capabilities all the time-so you can focus on shipping, too.
Reviews (1048)
Information Technology and Services
Feature-Rich and Easy to Integrate
Reviewed on Nov 09, 2026
Review provided by G2
What do you like best about the product?
A lot of useful features such as error tracking, feature flags configuration, session replays and source map upload to name a few. Easy to integrate with your application.
What do you dislike about the product?
The UI panel is a bit difficult to get around at first and it can also be slow to load if you have a lot going on.
What problems is the product solving and how is that benefiting you?
PostHog provides us with useful user information about how they use our application. We can then use this information to improve the usability of the platform.
Internet
All-in-One Product Analytics with Flexible Self-Host/Cloud and Easy Event Tracking
Reviewed on Nov 02, 2026
Review provided by G2
What do you like best about the product?
What I like best about PostHog is that it bundles product analytics, session recordings, and event tracking all in one tool without forcing us to stitch together three separate services. I’m Moritz Ecinu, Business Systems & Digital Operations Specialist at Santa Fe Digital Labs out in New Mexico. Most days I’m spinning up new SaaS tools, adjusting role permissions, troubleshooting webhooks, cleaning CSV imports, and walking our sales, delivery, finance and marketing teams through new platforms. We build custom websites and digital experiences for our clients, and we also use it to track how our own agency website visitors move through our lead flow. Before PostHog, we were juggling a few different tools: one for basic page analytics, another to watch user sessions, and a separate service just to set up custom event triggers. Keeping them synced and aligned was a constant hassle.
The self-host option plus cloud flexibility is a huge plus for us, but what really sold me is how simple it is to capture events right on the fly. I don’t need to bug our devs every single time marketing wants to track a new button click or form submission. A couple months ago, we launched a new case study download flow on our site, plus a calendar booking widget for discovery calls. I dropped in the snippet, set up custom events for each step, and built a funnel to see where prospects dropped off. It quickly showed that a lot of people started filling out the booking form but bailed when they hit the optional budget field. Our marketing team simplified that field, made it totally optional, and within a couple weeks our booked consultation numbers ticked up. That insight came straight from watching those recorded sessions and funnel data inside PostHog.
I also really value how easy it is to create feature flags. We often roll out changes to our client sites in phases. We can release a new UI tweak only to a small test group first, watch how users interact with it, and catch friction before pushing it out to all visitors. That reduces the risk of breaking a client-facing experience unexpectedly. It’s great for our agency work because we juggle dozens of separate client sites and don’t want to roll out untested changes blindly.
Permission controls work well for our team structure too. I can create restricted dashboards for our marketing lead so they can review funnels and conversion trends, without letting them modify event setup or feature flag rules. That keeps our tracking configuration consistent, and I don’t have to worry about someone accidentally deleting critical events we rely on for reporting.
The self-host option plus cloud flexibility is a huge plus for us, but what really sold me is how simple it is to capture events right on the fly. I don’t need to bug our devs every single time marketing wants to track a new button click or form submission. A couple months ago, we launched a new case study download flow on our site, plus a calendar booking widget for discovery calls. I dropped in the snippet, set up custom events for each step, and built a funnel to see where prospects dropped off. It quickly showed that a lot of people started filling out the booking form but bailed when they hit the optional budget field. Our marketing team simplified that field, made it totally optional, and within a couple weeks our booked consultation numbers ticked up. That insight came straight from watching those recorded sessions and funnel data inside PostHog.
I also really value how easy it is to create feature flags. We often roll out changes to our client sites in phases. We can release a new UI tweak only to a small test group first, watch how users interact with it, and catch friction before pushing it out to all visitors. That reduces the risk of breaking a client-facing experience unexpectedly. It’s great for our agency work because we juggle dozens of separate client sites and don’t want to roll out untested changes blindly.
Permission controls work well for our team structure too. I can create restricted dashboards for our marketing lead so they can review funnels and conversion trends, without letting them modify event setup or feature flag rules. That keeps our tracking configuration consistent, and I don’t have to worry about someone accidentally deleting critical events we rely on for reporting.
What do you dislike about the product?
One thing that consistently trips me up with PostHog is how spotty the bulk CSV imports are whenever I need to pull CRM data into visitor profiles. I’m Moritz Ecinu, Business Systems & Digital Operations Specialist at Santa Fe Digital Labs. Most days I’m spinning up new tool instances, sorting user permissions, ironing out webhook bugs, running integration tests, and walking our sales, delivery, finance and marketing teams through new platforms. We use PostHog to track lead behavior on our own agency website, plus a few marketing portals we build for our client projects. Every couple weeks, I export our known lead list from the CRM and upload it to PostHog, adding attributes like the original campaign source, assigned rep, and where the lead sits in our pipeline.
Time and again, longer text fields and multi-select tags don’t map cleanly. The import process will say it finished without any errors, but when I pull up individual visitor records, many of those custom fields come back empty or filled with jumbled text. This creates real headaches for us, since we rely on these properties to build segmented funnels for our nurture sequences. If those campaign tags are messed up, our marketing team can’t tell which ad sources are bringing in legitimate leads. The success notification from PostHog isn’t something I can trust, so I end up spot-checking hundreds of entries after every import. It eats up a ton of time I’d rather spend on other operational work.
I’m also disappointed with how rigid the alerting options are. I tried building a notification to let us know if form failures spike on our discovery booking page. You can set simple threshold rules, but trying to layer together filters for the specific page, error type, and lead segment makes the whole setup unstable. It’ll either ping us for harmless, random console warnings that don’t affect anyone, or stay completely silent when the booking form is actually breaking for multiple people. I spent an afternoon tuning the rule, and it just spammed our Slack channel with useless alerts. I wound up disabling that alert entirely. Now I have to pop into PostHog and review trends manually each day, which means broader issues can sit unnoticed for longer than they should.
My wish here is pretty straightforward. I’d love better field mapping controls for CSV uploads, with clearer previews before the import commits data. It would also help if the alert builder supported more intuitive, layered conditions without all that false-notification noise. Those two fixes alone would cut down so much of the manual validation work I deal with week over week.
Time and again, longer text fields and multi-select tags don’t map cleanly. The import process will say it finished without any errors, but when I pull up individual visitor records, many of those custom fields come back empty or filled with jumbled text. This creates real headaches for us, since we rely on these properties to build segmented funnels for our nurture sequences. If those campaign tags are messed up, our marketing team can’t tell which ad sources are bringing in legitimate leads. The success notification from PostHog isn’t something I can trust, so I end up spot-checking hundreds of entries after every import. It eats up a ton of time I’d rather spend on other operational work.
I’m also disappointed with how rigid the alerting options are. I tried building a notification to let us know if form failures spike on our discovery booking page. You can set simple threshold rules, but trying to layer together filters for the specific page, error type, and lead segment makes the whole setup unstable. It’ll either ping us for harmless, random console warnings that don’t affect anyone, or stay completely silent when the booking form is actually breaking for multiple people. I spent an afternoon tuning the rule, and it just spammed our Slack channel with useless alerts. I wound up disabling that alert entirely. Now I have to pop into PostHog and review trends manually each day, which means broader issues can sit unnoticed for longer than they should.
My wish here is pretty straightforward. I’d love better field mapping controls for CSV uploads, with clearer previews before the import commits data. It would also help if the alert builder supported more intuitive, layered conditions without all that false-notification noise. Those two fixes alone would cut down so much of the manual validation work I deal with week over week.
What problems is the product solving and how is that benefiting you?
Before we started using PostHog, understanding how visitors moved through our lead pages was really fragmented. I’m Moritz Ecinu, Business Systems & Digital Operations Specialist at Santa Fe Digital Labs. I spend my days setting up new tools, managing user permissions, troubleshooting webhooks, running data imports, and supporting our sales, delivery, finance and marketing teams. We build marketing sites and campaign portals for clients, and we also track our own agency’s lead flow. Back then we had separate tools for basic page stats, session recordings and event tracking. Getting all those pieces to line up was a constant hassle. Data never matched cleanly, and when marketing asked why leads dropped off, we could only guess.
PostHog pulled all that functionality into one place, and that’s the biggest win for us. We use it to watch visitor sessions, build funnels, and tag custom events without juggling half a dozen separate platforms. A few months ago, our team noticed lots of people starting our discovery call booking form but never submitting it. I built a funnel in PostHog and watched recorded sessions to pinpoint where people bailed. It turned out the optional budget input field felt intimidating for many prospects. We reworked that part of the form, softened the wording and made the field fully optional. After that change, form abandonment on that step dropped noticeably, and our sales team got more qualified booking requests.
Feature flags are another huge help for our agency workflow. We’re always rolling out small UI tweaks and content changes on client sites. Instead of pushing updates live to everyone at once, I can release changes to a small test group first. We watch how those users interact with the new layout, spot confusing spots or broken interactions early, and fix them before a full rollout. It lowers the risk of launching something that breaks a client-facing experience.
I also appreciate the flexible permission settings. I can share simplified dashboards with our marketing lead so they can review conversion trends, without giving them access to edit events or toggle feature flags. This keeps our tracking setup consistent, and prevents accidental changes that would mess up our reporting.
I won’t pretend it’s perfect. CSV imports can be unreliable, and the alerting rules are tricky to configure without getting false notifications. I still spend time validating uploaded CRM data and manually checking trends on a regular basis. Even with those rough edges, PostHog fixed our main pain point: disjointed visitor behavior data spread across multiple tools. It gives us clear, reproducible insights so we can refine our lead flow, reduce unnecessary friction for prospects, and make better calls on where to focus our marketing efforts. That saves me from maintaining a messy stack of separate tracking tools and frees up time for other integration and workflow work.
PostHog pulled all that functionality into one place, and that’s the biggest win for us. We use it to watch visitor sessions, build funnels, and tag custom events without juggling half a dozen separate platforms. A few months ago, our team noticed lots of people starting our discovery call booking form but never submitting it. I built a funnel in PostHog and watched recorded sessions to pinpoint where people bailed. It turned out the optional budget input field felt intimidating for many prospects. We reworked that part of the form, softened the wording and made the field fully optional. After that change, form abandonment on that step dropped noticeably, and our sales team got more qualified booking requests.
Feature flags are another huge help for our agency workflow. We’re always rolling out small UI tweaks and content changes on client sites. Instead of pushing updates live to everyone at once, I can release changes to a small test group first. We watch how those users interact with the new layout, spot confusing spots or broken interactions early, and fix them before a full rollout. It lowers the risk of launching something that breaks a client-facing experience.
I also appreciate the flexible permission settings. I can share simplified dashboards with our marketing lead so they can review conversion trends, without giving them access to edit events or toggle feature flags. This keeps our tracking setup consistent, and prevents accidental changes that would mess up our reporting.
I won’t pretend it’s perfect. CSV imports can be unreliable, and the alerting rules are tricky to configure without getting false notifications. I still spend time validating uploaded CRM data and manually checking trends on a regular basis. Even with those rough edges, PostHog fixed our main pain point: disjointed visitor behavior data spread across multiple tools. It gives us clear, reproducible insights so we can refine our lead flow, reduce unnecessary friction for prospects, and make better calls on where to focus our marketing efforts. That saves me from maintaining a messy stack of separate tracking tools and frees up time for other integration and workflow work.
Documentation A.
Instant Autocapture and Simple Event Tracking with PostHog
Reviewed on Oct 16, 2026
Review provided by G2
What do you like best about the product?
We installed PostHog on documentation.ai through Google Tag Manager, and autocapture started recording clicks and pageviews straight away. We didn't have to tag anything first. What we use most is how it joins anonymous visits to the person who later signs in, so we can follow someone from a blog post through to the product. The capture() API is simple. We send all our custom events (CTA clicks, demo bookings, pricing toggles, video plays, chat opens) through one helper. Adding a data-attr attribute to an element gives its autocaptured clicks a readable name without writing any code.
What do you dislike about the product?
Autocapture records clicks, but it can't tell identical buttons apart. Every signup button on our site says "Start for Free" and links to the same URL. To see which placement got the click (header, hero or a pricing tier), we had to write our own event with placement and plan properties. Loading PostHog through GTM also caught us out. Custom events pushed to the dataLayer don't reach PostHog unless you call it directly, and some events went missing before we noticed.
What problems is the product solving and how is that benefiting you?
It shows us which pages and CTAs lead to signups and demo bookings, so we decide content and layout from data. We also used its pageview data to find every 404 the site had served over six months. We redirected the most common broken paths and added a "Did you mean" suggestion to the 404 page. Without PostHog's records we wouldn't have known those visitors were being lost.
Information Technology and Services
Solid Analytics, Interface Could Be Fresher
Reviewed on Sep 23, 2026
Review provided by G2
What do you like best about the product?
I used PostHog from about 2021 to 2023 for analytics on client online stores, and it was fine and did the job back then. We're now in their startup programme and coming back to it for our own products, since we have a lot launching.
What do you dislike about the product?
Honestly I don't love the platform itself. They could improve it a little and modernise the interface a bit more.
What problems is the product solving and how is that benefiting you?
PostHog gives us product analytics so we can see how people use what we build, first on client stores and now on Culltron's own products.
Mazen M.
Easy to Use MCP & Agent Functionality—Session Replay Is a Game Changer
Reviewed on Aug 01, 2026
Review provided by G2
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.
Phil J.
A clearer way to connect experiments, sessions, and feature releases
Reviewed on Jul 27, 2026
Review provided by G2
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.
Ashley W.
PostHog Turns Raw Activity Into Meaningful Insights
Reviewed on Jun 17, 2026
Review provided by G2
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.
Amirhossein A.
PostHog Gives a Complete, Connected View of the Customer Journey
Reviewed on Jun 02, 2026
Review provided by G2
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.
Natanael G.
PostHog Delivers Clear User Visibility with Developer-Friendly Analytics
Reviewed on May 27, 2026
Review provided by G2
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.
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.
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.
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.
Mahdi H.
All-in-One User Behavior Visibility with Powerful Insights
Reviewed on May 25, 2026
Review provided by G2
What do you like best about the product?
What I like most about PostHog is how much visibility it gives into user behavior without needing multiple tools. We use it to track events, analyze funnels, understand drop off points, and monitor product usage in one place. Session recordings and feature level insights are especially helpful because they help us understand not only what users do, but also why they do it. It is flexible and provides a lot of value for product and growth teams.
What do you dislike about the product?
Because PostHog has many features and customization options, there can be a learning curve at the beginning. Setting up events and maintaining a clean tracking structure requires some planning, especially for teams without strong analytics experience.
What problems is the product solving and how is that benefiting you?
PostHog helps us understand user journeys and identify friction points across the product. It allows us to analyze onboarding behavior, discover drop off areas, and make better product and marketing decisions based on real user data instead of assumptions. This has helped us improve activation and prioritize changes with more confidence.