Array 1.17.0

Having launched major features in our previous release such as Session Recording and apps, over the past two weeks we worked extremely hard to improve PostHog's UX, enhance the new Beta features, and fix a bunch of bugs.

You'll notice PostHog feels much nicer to use and that's largely in part to all the feedback we've received from our users, so thank you and keep the suggestions coming!

If you're self-hosting and want to upgrade for a better experience with nicer features, remember to update your PostHog instance.

An important part of developing a great user experience is identifying, tracking, and fixing bugs.

With our new Sentry integration, you can leverage PostHog data to help your debugging, and Sentry exception data to track relevant UX metrics. As a two-way integration, it:

• Adds a direct link in Sentry to the profile of the person affected in PostHog
• Sends an $exception event to PostHog with a direct link to Sentry

If you're unfamiliar with Sentry, we highly recommend you to check it out - it is an awesome application monitoring platform of which we're avid users at PostHog.

To set up the integration you can read the step-by-step instructions on the dedicated Sentry Integration page.

RudderStack is an open-source, warehouse-first, customer data platform for developers. It allows you to collect and deliver customer event data to a variety of destinations such as data warehouses and analytics platforms.

As of last week, PostHog is now available as a destination on RudderStack, allowing you to send your event data from various sources into PostHog for performing product analytics.

You can read more about RudderStack on their website, and learn how to integrate PostHog through their comprehensive integration docs.

Over the past two weeks, our Apps feature was extensively worked on to improve the experience of using and developing apps for PostHog.

One of the main changes was the addition of app attachments, which allow you to upload files that are used in the configuration of the app, vastly expanding the realm of possibilities of what apps can do.

As a result of this, we built the PostHog MaxMind App, leveraging attachments to allow GeoIP data to be used for enriching your events. Once configured, the app adds IP-based location information as properties on your events, such as what country and city your users are located in, making it possible to create charts and tables filtered based on the location of your users.

Note: Apps are currently only available on self-hosted instances. If you're self-hosting and want to use the PostHog MaxMind App, please follow these instructions. If you want to build your own apps, check out our fresh new guide on how to do so.

Dashboards are a key part of PostHog, so it's important to us that you can have an overview of as many as possible of your metrics in them.

As such, the user paths graph and the retention table can now be added as panels on dashboards, making it so that every single chart, table, funnel, and graph you create in PostHog can make it to your dashboards now.

Following some feedback from our own Growth Engineer on what functionality we need for ourselves at PostHog, we have now extended the functionality of our 'Retention' view, adding first time retention and differentiating between 'Cohortizing' and 'Retaining' events.

In short, first time retention cohortizes users based on when they did an event for the first time, rather than adding a user to each cohort they had the event in. Additionally, by being able to have different target events for the cohort and the retention, you are able to track the impact of 'Event A' on the retention of 'Event B', exploring hypotheses such as how users who read your documentation retain on product pageviews when compared to other users.

In an effort to make it easier to filter through your events in PostHog and tag events that you find useful, we have now consolidated 'Events' and 'Actions' into one single view, found on the left sidebar as 'Events & Actions'.

On this page, you'll be able to manage everything related to your events, from inspecting their properties, to tagging them as actions. In addition, we have also added stats for your event and property volumes, so you can dig deeper into your analytics data collection, and optimize it to your needs.

Following a lot of great user feedback, we have now significantly improved our AWS CloudFormation Deployment.

We have now added configuration for relevant alerts and RDS disk size, as well as improved the setup flow and added automatic SECRET_KEY generation. If you're happy with the standard config, deploying with AWS is now just a matter of "click, click, click", as described by Karl, one of our engineers.

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!

A roadmap for various retention improvements that will significantly increase the power of PostHog's retention functionality.

Our community continues to be as awesome as ever, providing valuable feedback and helping out with issues, pull requests, and discussions on our Slack group.

This week, we want to give a special shoutout to Adam, who got 2 PRs merged and wrote an article about integrating PostHog on their website.

Check it out: Valuing user privacy — PostHog Analytics

Are you a Lead Designer, Fullstack Engineer, or Recruiter?

Or perhaps you're not either but think you'd still be a good fit for PostHog?

We want you!

In addition to the highlights listed above, we also merged a bunch of PRs improving PostHog's performance and fixing bugs:

• Fix Cohorts #2415 (timgl)
• Fix heroku image #2414 (timgl)
• Fix cohorts not being calculated #2404 (timgl)
• Fix navigation with actions & events #2401 (paolodamico)
• Minor fix: remove repeated code #2399 (paolodamico)
• Toolbar .less styles fix #2392 (mariusandra)
• Use cloud billing engine #2379 (paolodamico)
• Remove crontab manage events #2372 (EDsCODE)
• Increase action step url max length. Closes #2348 #2369 (timgl)
• Refactor sceneLogic to TypeScript and add dynamic page title #2361 (Twixes)
• Watch person and person_distinct_id tables for lag #2360 (fuziontech)
• Persist database after docker-compose down #2359 (adamb70)
• Adds features to cloud plans #2357 (paolodamico)
• Add missing copy over in dev.dockerfile for new config #2356 (EDsCODE)
• Added Revenue Data Generator #2355 (yakkomajuri)
• Closes #2347 Fix shared dashboards #2351 (timgl)
• Run E2E tests without celery #2344 (macobo)
• Add events table row count to metrics #2343 (fuziontech)
• Fix doubled up slack hook #2340 (EDsCODE)
• Trends consolidation #2339 (EDsCODE)
• Implement missing person datapoint on breakdown #2338 (EDsCODE)
• Fix 'Found 99 users' when there are more #2330 (yakkomajuri)
• Fix day interval for people #2328 (EDsCODE)
• Fix Hidden Properties Display State #2326 (yakkomajuri)
• Fix OR generation and deletion in cohort page #2324 (yakkomajuri)
• Fix gray bar under preflight #2323 (yakkomajuri)
• Fix local static file host on Windows #2321 (adamb70)
• Handle intervals don't rely on date_to for people #2317 (EDsCODE)
• Cache cohorts from clickhouse / make /decide fast #2316 (macobo)
• Make sure properties filter on breakdown #2315 (EDsCODE)
• Fix: Add default to params #2314 (macobo)
• Closes #2283 fix heatmap #2309 (timgl)
• Fixes email invite link #2307 (paolodamico)
• Closes #2286 remove restrict signups #2304 (timgl)
• Remove Live Actions Altogether #2303 (yakkomajuri)
• Add option to print clickhouse SQL to terminal #2302 (macobo)
• Basic caching for ClickHouse to redis #2300 (fuziontech)
• Fix cohort query missing filters #2299 (EDsCODE)
• Fix person created at #2288 (timgl)
• Updated rrweb block class #2279 (yakkomajuri)
• Fix Asterisk in action selector #2277 (timgl)
• Fix actions grouping by OR #2276 (timgl)
• Add tooltip to session recording, kill feature flag #2275 (macobo)
• Add data-attr to session recording toggle #2272 (macobo)
• Improve instance status report #2271 (macobo)
• Optimize @cached_function #2270 (Twixes)
• Make debug bar tricolor again and fix its text color outside of SPA #2269 (Twixes)
• Possibly optimize action finding #2267 (Twixes)
• Fix people filtering with entity filters #2265 (timgl)
• Don't reload sessions on closing player #2261 (timgl)
• Invite team member on sidebar #2259 (paolodamico)
• Fix team leakge in count #2257 (timgl)
• Make local events table work with proto from kafka #2254 (fuziontech)
• Add ee webhooks to celery paths #2250 (EDsCODE)
• 1999 improve feature flag ux #2243 (timgl)
• Maximize resuability between ch retention and pg retention #2241 (EDsCODE)
• Update changelog, mention npm requirement for session recording #2240 (macobo)
• Update rrweb, posthog-js dependencies #2239 (macobo)
• Navigation 1775 #2238 (paolodamico)
• Make sure instance status page loads on AWS #2237 (macobo)
• Fix actions count clickhouse #2234 (timgl)
• Make tiny adjustments to the changelog #2233 (Twixes)
• Log web access in docker #2230 (macobo)
• Disable server side cursors for PGBouncer #2229 (timgl)
• Avoid running cronjobs many times a day #2226 (macobo)
• Monitor clickhouse lag on cloud #2225 (fuziontech)
• Enable email on localhost by default #2222 (paolodamico)
• Fix flaky person test #2221 (timgl)
• Updated readme with heatmaps mention #2218 (jamesefhawkins)
• Prettier write instead of check #2215 (Twixes)
• Fix sessions on dashboard #2214 (timgl)
• Remove feature flags on clickhouse endpoints #2212 (EDsCODE)
• Add timing for event endpoint #2211 (fuziontech)
• Skip celery for ee path #2210 (fuziontech)
• Fix: improve the accessibility #2206 (weyert)
• Optionally log to Kafka for WAL #2205 (fuziontech)
• Plugins via NPM #2204 (mariusandra)
• ClickHouse dont run caching/cohort #2200 (timgl)
• Possibly fix org signup by fixing analytics #2199 (Twixes)
• Optimize commandPaletteLogic #2193 (Twixes)
• Remove some seemingly unused requirements and use pip-compile #2192 (Twixes)
• Fix suggestion loading error #2191 (timgl)
• Update Django from 3.0.7 to 3.0.11 (and Django-related packages) #2190 (Twixes)
• Center align retention values #2189 (EDsCODE)
• Update sentry-sdk from 0.16.5 to 0.19.2 #2188 (Twixes)
• Handle ChunkLoadError better #2187 (Twixes)
• Restore slack hook #2186 (EDsCODE)
• Update local dev to use proto for events #2181 (fuziontech)
• Fix Sentry issue POSTHOG-13K #2180 (Twixes)
• Ignore sentry error about mis-matched timezones for now #2174 (timgl)
• Fix feature flags clickhouse #2170 (timgl)
• Simplify action queries #2167 (timgl)
• New UI #2114 (paolodamico)
• Send invite over email if possible #2112 (Twixes)
• Save session player speed in localstorage #2110 (macobo)
• Improve weekly report testing #2014 (paolodamico)
• Run posthog-production CI in a way testing migration continuity #1863 (Twixes)

Ready to find out more?