We bring you the latest updates for Amethyst.

Analytics metric trends now show their share of the total

Search Analytics and User Analytics trends now show their share of the total. This is available for Total clicks and Total impressions in Search Analytics, and for Total sessions, Total unique users, Total sessions with conversions, and Total page views in User Analytics.

You can check absolute values alongside their percentages, making it easier to understand the relative size of the data that matches the current conditions.

Regular expressions are now available in custom channel groups

You can now add regular-expression matching conditions to custom channel groups in User Analytics.

You can group traffic with varying naming conventions into a single rule, making it easier to classify and compare the traffic you care about. For example, you can match part of a string or use ^ and $ for an exact match.

The Amethyst AI chat interface has been improved

The AI chat input, processing status, and conversation display have been improved.

• Multiple tool steps are grouped together, so you can follow their progress and see when they are completed, failed, or awaiting confirmation.
• The input area expands as you write, and analysis target mentions are easier to find.
• Conversation scrolling and display are more stable for long answers and tool results.

Minor Changes

Bug Fixes

• Fixed the Organic Search preset in User Analytics so organic traffic is filtered more accurately. It now uses the Organic Search default channel group instead of google / organic.
• Fixed an issue that could cause initial Search Analytics analysis to fail for large sites.
• For the Search Analytics GSC API data import feature, currently available only to selected workspaces, you can now select Search Console properties registered with your Google login.
• The feature can now split data imports for large sites or long-running operations across multiple runs and resume from where they left off.
• Fixed an issue where the month and year could not be changed in the second calendar when selecting a date range.