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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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.

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.

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. Review collected by and hosted on G2.com.

Honestly I don't love the platform itself. They could improve it a little and modernise the interface a bit more. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

I enjoy using PostHog for its analytics and visibility, which allow me to learn usage patterns from my users. The session replay feature is immensely helpful for getting feedback on user journeys through our platform, especially at the initial launch of SmushLabs.ai. PostHog is really clean and easy to use, making installation a breeze even for someone not so technical in marketing tools. The simple script installation through Node and the analytics working effectively, particularly with session replays, stand out to me. PostHog also has great visibility features and allows you to own your data. The session replays give me visibility on possible bugs and errors, and they help me understand the user journey through my landing page. The initial setup was incredibly easy; it was the best I've seen. Review collected by and hosted on G2.com.

Honestly thankfully I am a bit technical but looking it being used by other founders it might get a little complex. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

We mainly use it for product analytics and session replays and check it almost every day. It provides a lot of high-quality features for a website or SaaS product, and it isn’t hard to understand how to implement, even though there are many features it tries to walk you through. I also really like the app’s design; it looks great and genuinely feels like a passion project. Integrating it into both our website and our web app has been fairly straightforward as well. Their documentation site looks so good but is also helpfull. Review collected by and hosted on G2.com.

There isn’t really anything I dislike about it, but you do need to be at least a bit tech-literate to use it comfortably. Otherwise, it can feel overwhelming at first. That said, it seems like that’s exactly the kind of user they’re catering to. Review collected by and hosted on G2.com.

I enjoy the simplicity of using PostHog and the great team behind the project. The open-source aspect and the generous free tier are fantastic additions. The setup process was really easy to follow, making it convenient to get started. Review collected by and hosted on G2.com.

Nothing to share here. Review collected by and hosted on G2.com.