All Versions
Latest Version
Avg Release Cycle
22 days
Latest Release
146 days ago

Changelog History
Page 3

  • v1.16.0 Changes

    November 04, 2020

    Session Recording Page Screenshot

    Given that our mission at PostHog is to increase the number of successful projects in the world, session recording felt like a feature that fits in perfectly with that goal.

    PostHog already provides various features to help you understand and improve your UX - but watching real users use your product is a whole other ball game.

    πŸ‘€ With PostHog's session recording, you are able to truly feel the pain points of your users first-hand, seeing where they get stuck, debugging exceptions faster, and making your UX smoother.

    Session Recording Screenshot

    βž• Additionally, you can do so while still preserving the privacy of your users, by determining what shouldn't be captured, as well as being able to turn session recording on and off as you wish.

    However, please note that our session recording feature is in Beta at the moment. This means that it can be unstable and have bugs. To report bugs you find while using it, please open an issue for us on GitHub.

    ⚑️ If you have posthog-js installed via npm you will need to update to latest version.

    πŸ”Œ Plugins Screenshot

    Plugins is another Beta feature that we're extremely excited for. Currently only available for self-hosted instances, plugins allow you to add additional logic to your event processing pipeline, in order to do things like enrich your data or send it somewhere else, for instance to a data warehouse.

    πŸš€ At the moment, we have created a few example plugins for you to test out the functionality, and have the intention of launching more for the next release. We will also be launching tutorials on how to make your own plugins, so stay tuned for that.

    βœ… As of right now, if you're on a self-hosted instance, you should head over to 'Project' -> 'Plugins' to enable the functionality. You can start testing it out with our "Hello World" plugin, which adds a property to your events called foo with a value that is up to you to decide in setup.

    πŸ”Œ We also have built plugins for currency normalization and GeoIP data, allowing you to convert currency values in events according to up-to-date exchange rates and determine the location of an event based on the user's IP.

    πŸ“ˆ Our overall vision for plugins is to enable seamless integration with other relevant data analytics platforms, as well as allow users to more easily customize PostHog's functionality by adding their own logic and data to the event pipeline.

    Finally, as is the case with session recording, please report any bugs in the functionality on GitHub.

    Multiple Projects Screenshot

    You asked and we delivered!

    πŸ‘ As per feedback from many in our community, PostHog now offers support for managing multiple projects under one "umbrella" organization.

    This allows you to segregate concerns, such as keeping tracking for your dev and prod environments separately, as well as track multiple domains and apps without mixing data.

    In addition, we also enhanced our invite and permissioning system as a by-product of this feature.

    As this is an Enterprise Edition feature, please contact us at [email protected] if you are interested in using it.

    Dashboard Templates Screenshot

    🌐 In order to make it easier to create valuable dashboards to keep track of your business metrics, PostHog now offers the option to create new dashboards based on a template. We will be expanding the power of dashboard templates, but, as of right now, you can already create a dashboard using our web app dashboard template, which provides you with a good starting point for determining and tracking relevant metrics.

    Google Login Screenshot

    πŸ‘ In addition to GitHub and GitLab authentication, PostHog now supports signup and login with Google accounts!

    πŸ‘ We also improved our setup process by better structuring our settings pages, allowing you to change your project's token, and enhancing the UX for empty states on dashboards.

    πŸ“„ Docs Screenshot

    πŸ“š We have been working hard to improve our product documentation and had a few big upgrades recently:

    • πŸ“„ Our Docs now have a Dark Mode option
    • πŸ“š You can search our entire documentation without ever using your mouse
    • We are actively releasing new tutorials on how to use PostHog to track key metrics and improve your product
    • πŸ“„ Our Docs pages now load faster
    • πŸ“„ New screenshots have been added throughout the Docs, as well as functionality walkthrough videos

    …and a lot more!

    πŸ“š If you have any suggestions for new tutorials or improvements to our documentation, do not hesitate to let us know!

    We’re working hard to improve PostHog and would love to talk to you about your experience with the product. ⏱ If you're interested in helping us out, you can schedule a quick 30-min call with us on Calendly.

    Oh, and we're giving away some awesome PostHog merch as a thank you!

  • v1.15.1 Changes

    October 22, 2020
    • πŸ›  Fixed issue where 100s of emails would be sent. (oops!)
    • 🐎 Fixed performance issues with Redis caches filling up.
  • v1.15.0 Changes

    October 15, 2020

    Clickhouse Screenshot

    If you've followed our progress on GitHub over the past months, you'll know that ClickHouse has been the talk of the town.

    In their own words, ClickHouse is "a column-oriented database management system (DBMS) for online analytical processing of queries (OLAP)".

    Or, in simple terms: it's a very fast database.

    πŸ‘ As you may know, we have been using the well-established and reliable PostgreSQL until now, but from here on out our Enterprise Edition will be using ClickHouse instead. PostgreSQL remains a great option for lower volumes, but, for companies that handle huge event volumes, ClickHouse is a much better choice.

    On our cloud version we handle event numbers in the nine figures, and implementing ClickHouse has drastically reduced the execution time for all of our queries.

    If you're interested in using PostHog with ClickHouse, send us an email at [email protected].

    Command Palette Screenshot

    We're super excited about this.

    Last week we did an internal hackathon and the command palette was one of the awesome projects to come out of it.

    🏁 Now, when using PostHog, you can press ⌘K (Mac) or Ctrl + K (Windows) to reveal a Spotlight or Superhuman-like command palette that lets you navigate around PostHog mouse-less. In addition to navigation, the command palette also has page-specific commands that let you, for example, change the time range on charts, as well as a way to quickly share feedback with the PostHog team, create an API key, or even do some math with the built-in calculator.

    Eric, Michael, and Paolo got this done in just a few days, and we love it.

    Stay tuned for more exciting features that were built during the hackathon.

    Backend Feature Flags Code

    Based on community feedback, we made it easier for feature flags to be integrated with your backend, in addition to our frontend JavaScript implementation.

    πŸ‘ We've added feature flag support to our Python Integration, as well as improved the /decide endpoint used by feature flags to make the API experience better.

    We have ourselves been using feature flags with the Python integration to slowly roll out some exciting new features.

    Weekly Email Screenshot

    To help users keep up with their key metrics in a simple way, we have introduced a weekly email that gives you an overview of your active and churned users over the previous week.

    🐎 This is in Beta mode and we're expanding its capabilities, but it already gives you a good sense of your performance in terms of users.

    Have you gotten your weekly report yet?

    • [User Interviews](

    We’re working hard to improve PostHog and would love to talk to you about your experience with the product.

    ⏱ If you're interested in helping us out, you can schedule a quick 30-min call with us on Calendly.

    Oh, and we're giving away some awesome PostHog merch as a thank you!

  • v1.14.0 Changes

    πŸ“š Insight History Screenshot

    Eric really killed this one with a massive pull request where 55 files were modified.

    As a result, PostHog now allows you to look through a history of the charts you've made on 'Insights', so that you don't have to worry about forgetting the exact filters you used to reach a certain conclusion, or feeling bad about not having saved that perfect chart from a week ago.

    Experiment with insights all you want, now without the fear of losing your work.

    πŸ“š Personal API Keys Screenshot

    πŸ”€ We also merged another huge PR (58 files changed!) from Michael that's been a long time in the making because we wanted to get this just right.

    To facilitate integrations with external services, as well as make the experience of using our API simpler and safer, we have now introduced Personal API Keys. They can be generated and deleted on the PostHog setup page. It's worth noting that this is a private API Key, compared to your public 'Team API Key' used in the snippet.

    πŸ—„ Lastly, because of this change, we have deprecated authentication with username and password for API endpoints.

    πŸ“š Public Roadmap Screenshot

    At PostHog, one of our core values is transparency. As a result, we try to make as much information public as we can, from what we're working on to how we operate.

    πŸš€ As such, it felt important to us to release a public roadmap where our entire community can view what we're up to, what we'll work on next, and what our objectives are for the future. For a long time we have had a rough roadmap available in our Handbook, but, by now having our roadmap on GitHub, we can directly link issues to the board, and community members can also vote (with emojis πŸ‘) on issues they believe to be important.

    πŸ‘€ Furthermore, we have always encouraged members of our community to open issues for bugs, feature requests, or just anything at all they want to see changed. Now, issues opened by the community can be incorporated on the roadmap, so you can have an idea of how your suggestions fit in with our development process.

    Keep the tickets coming!

    As an open core company, we have to conciliate our open source efforts with our ability to generate revenue. Generating revenue is how we're able to continue to sustain our extensive work in the open source space.

    Thus, after a lot of brainstorming and calls with the likes of Sid Sijbrandij, CEO of multibillion dollar open core company GitLab, we settled on a business model that allows PostHog to be a sustainable company in the open source space. c πŸ‘― This led to the creation of two key things: an ee subdirectory on our main repo, and a new repository called posthog-foss. We'll be explaining these in more detail in the future, but, for now, you should know that to run fully MIT-licensed software, you can either clone the main repo and delete the ee subdirectory (without any consequences), or clone our posthog-foss repo, which is a mirror of the main repository without proprietary code.

    🐎 In addition, if you're an enterprise customer looking for added functionality and improved performance, contact us at [email protected] to discuss the license for using our proprietary features.

    πŸ”’ To ensure the security of your PostHog instance, it's important that you use a randomly-generated unique SECRET_KEY. This key is used by Django to encrypt cookies, calculate hashes, and generate tokens, making it of high importance.

    πŸ”’ Prior to this version, we denoted the importance of this in our Docs, but did not enforce it in our software. Now, to enhance security, PostHog will not allow you to run the server without setting it.

    πŸš€ Many of our deployments generate and set this key by default, so that you will not need to worry about it. This is the case with our Heroku One-Click deployment, for example. However, other methods may not automatically do this (we're working on it!). As such, if you run into any issues when updating PostHog, make sure you have a unique SECRET_KEY set.

    πŸ”§ You can find more information about this on our 'Securing PostHog' page and should always feel welcome to ask any questions on our community Slack group.

  • v1.13.0 Changes

    We're happy to announce that PostHog is now available as a destination on Segment.

    πŸ“ˆ Our friends at Segment have built a platform that works as an integrated data pipeline to pull in all your customer data. It's a cool way to combine PostHog with ie Google Analytics or Salesforce data.

    πŸ“„ If you're already a Segment user, check us out on their Destination Catalog. Otherwise, if you're dealing with multiple tools for data collection and analysis, consider using Segment! They have a generous startup scheme too, like us.

    We consolidated trends, sessions, funnels, retention, and user paths into one page for much faster answers to the questions you may have!

    PostHog has a feature where Actions can be posted to Slack or Microsoft Teams. This helps you notify your team in real time of the user actions that really matter. Just got a new user? Ping your sales team. Did a user try out a new feature? Get an alert!

    πŸ’» The integration used to be very basic - but now you can edit the message format directly in the UI.

    PostHog provides an irrefutably awesome toolbar. This lets you interact with your site or app and understand who is doing what. We've been in Beta for a few weeks, and spent a lot of time interviewing early users - thank you to everyone that took part!

    0️⃣ We have now eliminated many bugs and improved the UX, so this feature will be on by default for all new PostHog users.

    πŸš€ You can annotate graphs in PostHog - mention big releases, new features, or changes to your UX.

    Now, it's quicker and easier to get a quick read on what happened that caused something funky in your graphs.

    0️⃣ We've also made all annotations default to being global. That means if you create an annotation in one graph (or in the annotations page), it is visible across any dashboard graph that covers that date range. No need to fear losing your annotations.

  • v1.12.0 Changes

    • Shared Dashboards

    Dashboard on a TV in your office? Want to have a public stats page? Share a dashboard with someone who doesn't have a PostHog account? You can now publicly share a dashboard. Just click "Share Dashboard" and enable sharing. You'll get a link that's publicly accesible.

    πŸ”„ Changed your mind? You can always disable sharing.

    • Aggregate Functions

    πŸ’» Want to know the average revenue per user? Want to know the lowest browser version anyone is using? You can now do Sum, Max, Min and Avg calculations on any event property and graph them in trends!

    • Global Annotations

    πŸ›  Digging through git commits to find out what changed to make the graphs go hay-wire? No more! You can now annotate when something happened (a big release, a bugfix or a launch) and make it super easy for your team-mates to figure out what's going on. Now global.

    As part of this, you can now also manage, add and delete annotations from a central screen.

    • Funnel Step Time

    πŸ‘€ You can now see how long it takes users on average to get through steps in a funnel.

    • Regex Filtering

    Regex master? Put those skills to use on any property with regex filtering

    • Retention Table Improvements

    Previously the retention table was hardcoded to only recognize the $pageview event as a retention event. Now, you can select any action or event to measure retention on.

    Clicking on any section in the retention table will tell you exactly what users fall in that item.

    πŸ› Bug Fixes and Performance Improvements

  • v1.11.0 Changes

    • Annotations

    • Cohort filters

    • Retention table filtering

    • πŸ›  Many toolbar fixes.


    πŸ› Bug fixes and performance improvements

  • v1.10.1 Changes

    July 02, 2020

    πŸ›  Bugfixes

    • πŸš€ Actually include the version bump when you push a release! πŸ›
    • πŸ“„ Add flutter docs and reorder flow #1134
    • Black all the things! #1136
  • v1.10.0 Changes

    July 01, 2020


    • It's like inspect element, but for user data.


    • πŸ‘€ Easily see the ranking of which parts of the page your users are interacting with the most:


    • We learned a ton about our product and website within minutes of trying this out.

    toolbar dance

    πŸ”‹ Feature flags

    • Feature flags let you roll out changes to users with a certain property, or to a percentage of users, or some combo of the two.

    feature flags

    Other exciting, enthralling and invigorating features

    • πŸ“„ Flutter Integration. You asked for it and now it's here!
    • Retention page. PostHog already had stickiness, but now there is a table that demonstrates perhaps more clearly how your users are coming back (or not!)

    retention view

    • πŸ‘ Better onboarding. We've had a go at redoing how our set up flow works, and will be tracking if it helps more people get through PostHog's own funnel!
    • πŸš€ deployment. A very simple, new and trendy way to get up and running!
    • 🌐 Porter development. Join the cool kids and do web development in the cloud. Thank you so much to porter-dev for creating this PR.
    • Event name filtering. By popular demand, you can now filter the events table by the event name. Happy debugging your implementations!

    filter by event name

    πŸ› Bug fixes and performance improvements

  • v1.9.0 Changes

    June 18, 2020
    • Sessions view sessions overview
    • πŸ‘€ You can then see exactly how a user interacted with your app: sessions more detail This should really help with debugging, or just trying to get a detailed view of what users are up to.

    πŸ‘ Better testing

    πŸ“„ Develop PostHog with Porter

    Management command for millions of events

    Set properties to anonymous users

    πŸ› Bug fixes and performance improvements