Changelog

Responding to feedback from our customers, we have decided to no longer require two-factor authentication (2FA). It appears that this decision annoyed many users, and we totally understand.

Why did we do this? We believe it's our responsibility to enforce good security practices. Security is that kind of thing we have to go through but no one enjoys. However, it's also what keeps our back when things go south. We also get that the timing matters and most of us would like to do it when the timing is right.

So what now? For those who have already enabled it, there's nothing more you need to do—congratulations :) For everyone else, we have temporarily disabled this requirement. We will introduce an alternative for those who cannot or do not want to use a third-party app for authentication. We are considering adding email-based OTP.

• Fixed a bug in the invitation process when adding new team members to an organization.
• Fixed a possible issue in the SDK JS v2 that could result in high CPU usage on Chrome.
• Fixed an issue that required users to re-login more than needed.
• Fixed an inconsistency/display issue in the funnel when Users Retention from First Step was selected.

New authentication mechanism:

• SSO now uses SAML2 standard.
• Improved user flow for the invitation and sign up process.
• Enhanced security.

Various UX improvements:

• Improved label(s) edition for multiple events at once.
• When splitting a funnel by user segments, even empty user segments are now displayed which is more user friendly.

Other release notes:

If you encounter the error "Error while loading the account" in the Chrome Plugin, make sure you are using the version 3.8.0 or superior. Your browser should update this automatically when restarting your browser. You can check the current version in the Details button as below (usually in the Extensions menu of your browser).

Brand new pixel

We've just launched an updated JS SDK that's faster and lighter.

Why a new pixel?

This new version incorporates several improvements over its predecessor. Despite our current pixel already being one of the lightest on the market, our team managed to reduce its size from 40kB to 37kB, making it 8% smaller. While this may not seem like much, in the realm of UX, every byte and millisecond count!

The new pixel utilizes Brotli compression instead of Gzip, leading to faster decompression on the browser side. Our benchmarks indicate that the previous 24ms decompression time has now been reduced to 11ms (the lower, the better!). Once more, every millisecond counts.

In addition to its reduced size, we've updated the pixel to keep pace with the rapidly evolving web landscape, ensuring compatibility with the latest browser features. This also opens up new possibilities for future Air360 capabilities. Stay tuned!

How to update?

Just replace the previous pixel you had for Air360 with the one from our quickstart here: https://app.air360.io/docs/getting-started/#on-your-website Note: If you installed our pixel after 3rd of January 2024, you have nothing to do.

When to update?

There's no rush. The current JS SDK will continue to receive support until August 1st, 2024. However, we encourage you to update at your earliest convenience for optimal performance.

Session replays

• Various performance improvements on session replays.
• Ability to hide HTML elements from the session replays without any code. See how you can do this here. (Available only with new pixel)

Chrome Plugin Fixed a glitch on exposure rate calculation that affected some page under some specific conditions.

Status page A status page is available from the app and from https://www.air360.io/ as well (footer).

Various UX improvements

• Events definition can be seen even when they're in progress.
• User segments can be selected using search dropdown in funnels.
• When a user segment was selected as a dimension, it wasn't shown if no visitor were in the funnel. This wasn't intuitive. Now, user segments are returned even if they do not contain any visitor.