PostHog Reviews: 4.4/5 — Solid Choice

The recordings are by far the best feature. It even worked through our proxy. The UI is also great, and the live responsiveness is impressive.

We work with vue and I feel that posthog is missing some basic client library integrations. More tech specs from the user would be nice.

Our main product is a dashboard application. We badley needed to see what our clients were actually using the app for. Posthog recording helps with that.

The product is open-source, and the team is very hands-on and receptive to feedback

PostHog's analysis tools do not perform well when you have a lot of data

Experimentation and analytics

Easy to use and good API to implement it with python or other stacks

From a BI perspective, we would like to push data regarding the Users, to add information about them that we in our databases. But we are facing many issues while doing this, even using their API

Getting more insights about the use of our app than using other tools like google analytics.

The user journey recordings are great! Also, the funnel logging.

It is hard for us to get the aggregate dashboards that we want. An example would be how many users opened the app/website in the past month.

We want to understand what our users are doing and how our funnels work.

I like the autoevents. this looks quite usefull. Sending in you own events seams quite easy as well. The fact that there is support for A/B testing, heatmaps and session replays is awsome

The reporting is a bit lack luster. This might be a user problem, Im not that well versed using this tool. But i find it hard to find reports on events that inclide event parameters

The fact that this can be self hosted, and that the data can be stored in Europe is a big pluss comapring it with GA, where you have no controll over where the acuall data is stored.

The best part of the Posthog is Insights and recordings,

Very little documentation, and tutorials, for example identifying users, was really hard

It helps us to understand user behaviour and analyze their data

I am able to log in and see issues client have experienced and pinpoint problems.

It can be glitchy. Sometimes we get server errors, nothing will load or it takes a long time to find what I am looking for.

Session replay is what I personally use posthog for. I am able to see what the client is experiencing and pinpoint pain points or bugs in our product.

That I can view quite a large number of datasets

There seems to be too much of a learning curve in setting up a dashboard

Viewing data of user's and their usage of our product

Pricing and documentation. The UI is also great and quite intuitive to navigate around.

The video session recording is not as good as I hoped it would be. I notice that fonts in our React web application don't look the same in the video recordings and there are other little UI things that don't 100% match the UI. Additionally, the layout with the side-by-side video + network request timeline is very "squeezed". IMO LogRocket's layout is better in this regard. I also find the video recordings to be janky at times.

We would like to better understand what is happening when a user faces an issue and video recording seems to be promising to help us achieve this.

Open source, integrates very easily on the website. I like the recordings and the fact it has features from other services.

I am a bit upset about the pricing. I also found it tough as a PM to set events so that I can track things. Heap was on the other hand very very much easier. I didn't have to involve the engineers so often.

Tracking active users, funnel usage, location data, session, mobile/desktop, etc.

It's wide array of tools to use to track user behaviour

Lack of product tour, lack of step guide. Unfriendly to non-coders

Funelling to see how users land or miss each page

I like how really simple it is to interact with PostHog's APIs.

I don't like how there isn't a lot of support for the Java SDK.

It's allowing me to easily A/B test.

I think it is great as an idea and helps a little with early product tracking. Setting it up was not bad as well. it is also great that it is free for 6 month for startups, so trying it out is low commitment.

The usability of auto-capture and heatmaps is definitely more overhyped than it actually is helpful. I came into this with an expectation that very minimal coding will be needed to capture events and flows from the Front end. But it is very different. I can see that auto-capture is not consistent enough to fully rely upon. Sometimes we designate a button as an action, but not always a user action will be caught as exactly that action. Basically, it becomes quite obvious early on that you still need to define actions in the backend. This is what all other tools already do, so I expected PostHog to be different but it is not. I also tried reaching out to the team a few times about questions around this but still got no answerback. So i expected to use this to a high degree in my product role with no engineering help. And it's not working like that.

I can easily track user paths, which I was not able to do before. It also helps with recordings as we use that moslty for insights, as Heatmaps and Autocapture is letting us down

PostHog is very configurable. You can create cohorts depending on lots of different fields and information. User Session replays are a game changer.

Feature flags cannot be controlled by the current URL. It's kind of expensive.

Thanks to PostHog, we know what our users are doing on our page and how they're interacting with it.

- Ease of use - Ability to quickly check live events to deep dive for RCAs

- Unable to do complex calculations for visualization - Slow load times

API response times API success/failure App downtime Feature usage

Data visualization is great, which allows us to have recurring graphs we look at weekly. Comparison across time periods is also great. My favorite part are the footages when considering bug related graphs.

I don't find it too easy to program the graphs as a non-tech person. It is less intuitive than Retool, even though Retool is not no-code. Also, we cannot import the PostHog graphs to show them to our clients/customers.

The problem of organizing our visit events and our main bugs. It allows us to quickly check some bug occurrences and watch their footage, which is great for fixing them.

Really enjoyed user pathing/flows. It was great for an early platform to get an understanding of where it is users traffic most when dev resources internally are limited.

Its utility is great until a lot of features, especially ones associated with user insights, seemed to get axed or kneecapped. It's also not as user friendly in terms of UI/UX, I find myself rage clicking quite a lot and if you're a non-technical PM it becomes more of a dev task than needed. With the LOE put in, we'd be better off pulling data from a BI tool like Metabase or PowerBI and leveraging our Product/Data Analyst's time to draw deeper insights ourselves.

Honestly, none at this point. We've basically churned out. I was the one championing to use Posthog upon our launch because of its self-hosting option.

Flexible and easy to combine various data sources to give data insights

Does not replace google analytics as it does not do the usual landing page analytics out of the box

Analytics

1. Interface is very nice 2. Integration is simple enough 3. I can share dashboards by link (without anyone having to login) 4. Customer support answered relatively quickly.

1. I'm unable to quickly delete events 2. I'm unable to share "Live events" (or have "Live events" as a separate dashboard and then share the dashboard) 3. Number of features can be a bit overwhelming and I feel too scared to even start exploring. 4. Excluding events by attributes isn't working consistently. 5. Can't click on "N persons" in Funnel view to see the list of people in it.

Our product are software solutions for other companies developed on our AI platform. Posthog allows us to share KPI data with our clients through anonymous dashboard, without us having to developing (and maintain) things manually.

It was easy to setup and start capturing data.

All of the out of the box examples appear to be geared at public applications and focus on metrics like user retention, etc. Our app is B2B. We are more interested in usage analytics. Getting the metrics we want has been painful so far.

None yet.

Many features, quite modern looking and not as hard to grasp as Google Analytics (still hard though).

Hard to find all of the features (UI could be arranged better). I am missing a feature to comment on a video recording for instance.

I can see recordings of interactions in the app

There are a ton of options and a lot is pre-configured right out of the box. The toolbar is really convenient, too. It makes creating actions really easy.

The documentation seems to assume the user is already familiar with Posthog. I've found the documentation frequently skips over the real questions to focus on features. I don't need to be sold on the features again; I need to know how to make them work.

My company wasn't using any analytics software before installing Posthog, so it's already giving us a better idea on what users are actually using on our pages. The session recording is proving very valuable for our design team as well.

Simple set of features that work well. Didn't have any issue setting up flags and using it in the codebase.

I did't like that I had to set up the same flag twice for the development & production environment.

It makes feature flag management easier.

pretty easy to setup. automated usage analytics is definitely the future. feature flags are solid as well.

the overall user experience is not great. multiple users from our org detest using the app and find it difficult to create reports. some features just flat out don't work.

it's a solid feature flag solution for us, but we've decided to move to another platform for product analytics

Much better than Google Analytics with a great self host model. The visualizations and charts are better than Google Analytics too, and even Heap.

Missing key features such as elegantly supporting multiple environments (they mix the concept with projects) and lack basics like breaking down reports by multiple dimensions. This latter issue has been a feature request for almost 3 years.

Better experience than google analytics which helps given you more usable insight for nominal cost. Smarter data model than GA too giving more power in your queries.

We liked the concept, but since the product cannot function at any reasonable scale, I can't say there is a lot that I like about it.

We were enthusiastic early adopters of the product over one year ago, and I can now safely say it has been one of the worst business decisions we have ever made. I utterly regret trusting such an unfinished product with our valuable data. We started when the Posthog was running on Postgres. Despite throwing loads of Heroku resources at the problem, within weeks, the dashboards became unresponsive and unusable. All of the dashboard queries were timing out. They knew this, and there was hope in the new Clickhouse backed instances. They market "one-click deployment." The reality of getting the Clickhouse based Posthog cluster running is FAR from "one-click." We spent nearly a week debugging issues. After which, we were unable to transfer our data completely. We hopefully ran the migrator around 10-20 times, but it failed to copy all the data and always left huge gaps. We've spent over two months trying to get it to work. The team has appeared willing to help but has not addressed the problem. They usually say "looking into that" and then never reply. I think the product has spiraled out of control. I've burnt my fingers with this product, and I hope prospective Posthog users will avoid repeating my unfortunate error in trusting this product. Don't use this product if you value your time or your data. We've now abandoned the product and our data.

We want to monitor our product analytics, but this dream has not yet been possible. We are less productive due to trusting in Posthog. Our business performance has deteriorated due to wasting development time trying to debug Posthog.