Changelog

Chrome Plugin bugfix:

• We've resolved an issue where errors could occur when selecting a large number of elements on extensive HTML pages using our Chrome Plugin. [Fixed]
• No need to update your Chrome Plugin, the fix is applied automatically.
• Speed should be also improved.

New Chrome Extension released 👇

Security Enhancement: The Chrome Extension now features enhanced security with its own dedicated authentication system, ensuring a more secure and reliable experience.

Improved on-page analytics experience: Improved ability to adjust the definition of the element when using the zoning. You can now adjust the definition used when analyzing a given HTML element directly on the page.

🎉 Autosave 🎉: This has been a highly requested feature that will save you a significant amount of time. Until now, any page analyzed with Air360 Chrome Extension would lose the selected zones once the extension was closed, resulting in a considerable loss of time. Now, the extension automatically saves all your zoning on a given page. It also preserves any updates you have made to how certain HTML elements should be analyzed (with text, without text, etc.).

How to benefit from this feature?

There is nothing for you to do; the autosave functionality works seamlessly in the background, automatically saving your settings and progress for you.

🎥 Video explanation here! 🍿

Air360 pixel v2 updates

• Improved tracking of some error events
• Improved how scrolls are detected within a page

New event creation

• Enhanced preview functionality now shows the number of users and event occurrences when defining a new event.

• Sometimes session replays were not correctly stopped when the cookies were opt-out in the pixel v2 [Fixed]
• Resolved an issue that prevented the preview from refreshing correctly when creating a new event in the dashboard [Fixed]

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).