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.