Product Updates

We now support multi-currency revenue analysis, allowing teams to ingest local currency values and view them consistently in their project’s target currency. With support for daily exchange rates based on transaction dates, customers can analyze revenue data without the need for manual conversions or preprocessing.

Since Currency Conversion depends on Derived Properties, we’ve also made Derived Properties available directly within the E-Commerce package.

Previously, Derived Properties were only accessible to Enterprise customers. With this update, both Currency Conversion and Derived Properties are now available to the following plan types: Enterprise, Growth, and Scholarship.

How to access:

• Send the $currency property (3-character ISO 4217 code) alongside $revenue or $price.
• Access derived fields (ootb & custom): Data → Properties → Derived
• Use these for filtering, grouping, and aggregating in charts.
• Use custom derived properties for advanced use cases (e.g., cart properties). Set your project’s target currency in Project Settings.

When: This is now live

• We now support targeting Group Cohorts in Feature Flags and Experiments with Remote Evaluation. Group Cohorts have long been supported for Local Evaluation, but until now, Remote Evaluation lacked this capability due to the absence of Group Cohort Sync support. • This release is a cross collaboration with the Activation team to support Group Cohort sync and targeting in Experiments.

Why: • We now support group-level cohort targeting for all kinds of feature flags and experiments. • Also, optimizations were made for the cohort sync with a new architecture for group cohorts.

When: • This feature is GA.

Description: Customers now have an audit log of all the changes made to flags in one place, so they can correlate spikes in metrics to changes in flag rollouts.

Why: Simplifies feature flag auditing.

Where: This feature is available now.

Help doc: https://amplitude.com/docs/feature-experiment/notifications

We improved device and OS categorizations to classify Mac devices, Android devices, and other variations more accurately. Improvements include:

• "Mac" cases now go to desktop (previously it looked for more specific variations like "macOS", "macintosh", etc.).
• Adjusted Android device categorization to better handle cases previously categorized as "Other" by refining the logic to detect specific strings like pinterestbot rather than just pinterest.
• Enhanced categorization of devices with the Silk OS to distinguish between Tablet (Kindles) and TV.
• Updated Android categorization to cover more device types while maintaining existing logic to handle the diverse range of Android devices like tablets and TVs.

Description: Event-level property deletion allows users to delete properties from specific events, while keeping them active on others. This allows for data clean-up that was previously not possible.

Why: Previously, when the same property was sent to multiple events, there was no way to remove that property from a single event. A property that was sent accidentally or needed to be deprecated couldn't be cleaned up, which was especially frustrating for customers who want to maintain clean data.

Where: Data Product -> Events Page -> Select an Event -> Properties section in Details tab.

When: Available now on all plans

Description: On every page load, we now automatically add a filter to the Guides and Surveys table that filters out archived guides and surveys. This way, we never have to load archived data, which makes loading the Guides and Surveys dashboard much faster. In addition, we implemented bulk archive capabilities, making it easy to keep the number of non-archived guides and surveys manageable.

Customers: This is available for all customers.

When: Available now.

Description: Create custom, high-quality templates of guides and surveys for your team to reuse. This can include custom designs and/or unique trigger and targeting rules. Bonus: Preview templates directly in the create flow modal!

Why: Duplicating guides and surveys can get messy, and it's hard to stay organized. With templates, users can easily find 'approved' templates through the natural create a guide flow.

Where: Create a new template via the settings dropdown when viewing a guide or survey. Once created, Templates are hidden by default to give you space to polish them up, and you can 'unhide' them when you're ready for your team to use them.

When: Today, for Enterprise customers

Description: AI summaries for survey responses are here! These are essentially what they sound like: get quick insights into your long-answer survey responses by seeing an LLM-generated overview of what users are saying.

Why: This allows our users to gain insights into how their users are responding to their surveys much more quickly without having to slog through a bunch of individual answers.

Where: This feature is available now within the Insights tab on any survey with a "long answer" survey type.

Available in EUDC: Yes

When: Available now for Growth & Enterprise customers!

Description:

• Before: Once a guide or survey was triggered on the right page, it would continue to appear on all pages until it was completed or dismissed, unless you used "Temporarily hide if".
• Now: The new "hide on all pages that don't match the above rules" is enabled by default. This causes the guide or survey to disappear on every page that doesn't match the page targeting. Users can use the previous behavior by unchecking the box.

Why: This was one of the bigger behavior changes made while integrating with Amplitude. The assumption was users would quickly dismiss or complete guides, so their showing on other pages while "active" wouldn’t be an issue. However, that concept was never intuitive for customers. This change aligns behavior with user expectations while still providing full flexibility if needed.

Where: Within the "Trigger" panel of the Guides and Surveys builder's "Setup" tab.

Available in EU: Yes

When: Live for all Guides and Surveys customers. Existing guides and surveys without "temporarily hide if" conditions were migrated to use the new default behavior.

Description: We’ve redesigned the heatmaps list page with a new gallery layout that shows off colorful previews of your heatmaps! For those without previews, we’ve added delightful placeholder images.

Why: Heatmaps are a powerful visual tool, so we made the heatmaps list page more visual too! The new layout is warmer, more intuitive, and makes exploring engagement data feel even more delightful. If you prefer the previous table view, toggle back with the dropdown!

When: It has been rolled out to all Heatmaps customers.

Description: You can now press a button in the UI, and it will automatically translate your guide into all the supported languages using AI.

Why: Customers with applications that support different languages want to display guides and surveys in the correct language. If you support multiple languages, keeping them up to date becomes tedious. We already offer an API that you could use to automate this yourself. But, not everyone has the engineering capacity to do that.

Customers: Very handy for anyone using localization.

When: Available for everyone using localization (growth and enterprise).

Description: The Resource Center is a new embedded launcher and widget with search, personalized recommendations, and useful links.

Why: The Resource Center lets customers build targeted recommendations, surface guides, and activate new features in a non-intrusive way.

• Customers can connect their website, documentation, or help center and automatically pull in relevant articles.
• For users, they can read documentation and access important links without leaving the app.

Where: Nested under Guides and Surveys > Resource Center.

Available in EUDC: Yes

When: Available today! (For all customers with G&S access - no new SDK required)

Useful Resources:

• Documentation

Description: Small update to web experiments to support control variant editing. This lets users iterate quickly on their web experiments on the same surface without needing to actually deploy the changes to production before running their next test.

Available in EUDC: Yes

When: Now available for all Web Experimentation customers.

Description: Added fine grained controls for each setting in Autocapture in the Browser SDK. Previously Autocapture could only be turned on or off, this allows users to have much more control over how Autocapture functions on their website.

Why: This enables clients to configure individual Autocapture settings without a code deploy. This decreases turn around time for new customers onboarding and helps Amplitude users update settings without relying on engineering or requiring multiple releases.

Where: Data > Settings > Autocapture

When: Available to 100% on any plan with either:

• Browser SDK version 2.10.0 or higher with fetchRemoteConfig set to true.
• Browser SDK version 2.16.1 (enabled by default)

Description: You can now scope your experiments to specific URLs using Pages—a new way to define and reuse targeted page contexts. Pages improves targeting precision, reduces test spillover, and supports SPAs and dynamic websites. You can also assign custom code and URL redirects to individual Pages.

Why: This enables marketers and PMs to run more precise, reusable, and isolated experiments without affecting the broader site—making it easier to iterate quickly and scale experimentation across teams.

When: Available to all Web Experiment customers

Description: You can now include cart properties as filters when creating custom events! This makes it easier than ever to define custom event logic based on what's in the user’s cart — think product IDs, quantities, prices, or categories.

Why: Previously, customers couldn’t use cart-level properties when defining custom events, limiting their ability to tailor event definitions around commerce behavior. With this change, teams can now construct more precise, expressive custom events — for example, creating an event for “cart contains product X.” This unlocks richer downstream analysis and conversion funnel tracking for commerce-focused teams.

Customers: This is especially valuable for retail and e-commerce customers, but any team using object array properties will benefit.

Description: Filter on any columns (like created by), use complex operators, and have your filters now persist across web sessions!

Why: We’ve received a bunch of feedback for better filtering—this change drastically levels up our filtering capabilities.

Customers: All customers

Available in EUDC: Yes

When: Live now!

Description: Create and add custom tags to make organizing guides and surveys easy!

Includes:

• Search/Filter your guides and surveys by tag names
• Rename tag names or add a description to make them clearer for others
• Bulk add/remove tags from many guides and surveys with multi-select in nudge table
• Tags are included in all guide and survey events, too!

Why: This makes coordinating lots of active guides and surveys amongst teams easier.

Customers: All customers

Available in EUDC: Yes

When: Today

Description: Instead of just being able to specify how many times a guide or survey should trigger per day/week/month, you can now quantify the period as well. It’s a small change for us, but it is very effective. Bonus: There is a year option now as well.

Why: Customers want to display guides and surveys on a recurring basis, such as every two weeks. Currently, they may have mapped it to “2 times per month.” However, depending on the trigger setup, the guide would have likely appeared twice at the beginning of the month and then stopped. Now, they can set “1 time per 2 weeks,” and it will correctly show up every two weeks.

Customers: It’s a fairly basic feature that we believe will be widely used.

Available in EUDC: Yes

Description: We’ve introduced two small improvements to Surveys: the ability to view survey insights as charts directly in-product, and the ability to export raw survey responses to CSV. These updates make it easier for users to visualize and share insights from their surveys and analyze results outside the platform.

Why: Customers previously lacked easy ways to explore and communicate survey insights or to conduct deeper analysis offline. With charts, users can instantly visualize response trends without needing to build their own visuals. CSV exports allow teams to further slice, analyze, or combine survey results with other data sources in their preferred tools. These changes unlock faster, more flexible survey analysis.

Where: Navigate to any survey, and you’ll see in survey insights it now has a button to create as new chart. Survey responses now also have a button to download as CSV.

Available in EUDC: Yes

When: Available now in GA for all customers with access to Surveys.

These beta enhancements for cart properties are now generally available! This is a huge leap forward in making nested cart data more powerful, usable, and trustworthy across Amplitude. Here's a summary of the recent changes that are now live for everyone:

• Full Platform Support: Cart Properties now fully work with Event Block, Metrics and filters, Segment creation and group-bys, Funnels (with holding constant), Data Tables (columns, rows, filters)

• Lookup Table Support for Cart Properties: Translate values like SKUs or brand codes directly within carts into human-readable formats

• Transformations for Cart Properties: Extended support for certain merge/rename transformations

• Derived Properties with Cart Analysis: Introduced Parallel Operators to Derived Properties. Note: operators that don't currently work properly with array/cart properties are IF, CONCAT, regular math operators (SUM, SUBTRACT, MULTIPLE, DIVIDE, need to use the PARALLEL_ versions).

Description: An official public endpoint for downloading local evaluation model flag and experiment objects. Useful for customers bootstrapping client-side applications with local flags and edge evaluation use cases. Previously, customers had to use the internal endpoint, which was undocumented. Now we have official documentation on how to access the configurations from the API and bootstrap SDKs.

Where: Developer Docs

Available in EUDC: Yes

When: Now!

Description: Customize content in guides and surveys by dynamically displaying user properties (must be available client-side). Includes UI for enhanced visibility and ease of configuration.

Why: Personalized messaging is more robust and effective. With personalization, now you can do things like:

• Catch a user’s attention by using their name
• Guide users directly to their appropriate email/phone support hotline

Customers: Only available for enterprise customers

Available in EUDC: Yes

When: Today

Useful resources: Demo clip | Help Article

Description: Provide clearer paths for support and demos during onboarding phase.

Why: There are so many ways to get help on data setup, but they weren’t centralized in a helpful/non-overwhelming way. We created a Resources sidebar to centralize them, and we added a link to our Slack community where people can get 1:1 support from our Community team as well as the broader Community members.

Where: In the onboarding page

Available in EUDC: Yes!

Description: Guides and Surveys can be localized by setting the language during initialization. With this addition, you can now update the language mid-session.

Why: Customers should still try to set the language during initialization. Otherwise, we might show a guide in the wrong language before the correct language has been set via updateLanguage. However, there are valid use cases for updating the language mid-session. For example, using the default language for unauthenticated users, but once they log in, switching to the user’s configured language.

Available in EUDC: Yes

When: Available for everyone using localization (Growth and Enterprise customers).

Description: Before, test and preview was only available when in draft or test instrumentation mode. Our customers want to be able to preview variants while a test is running or after it’s completed. Now, you can test and preview anytime, anywhere, in just two clicks.

When: Available Now!

Customers: All customers

Description: Redesign of usage tab on cohort details page and cohort archive modal to better show how cohorts are used across blades.

Why: Provides customers a clearer picture of how their cohorts are used in charts, experiments, etc., and the additional use cases they can unlock. In the archive modal, this acts as a quick but critical check to ensure charts, experiments, and other objects will not be broken by archiving a cohort; initial data shows customers spend at least 10x as long on archive modal with usage data, and these cohorts are archived 35% less.

Where: Cohort details page and cohort archive modal (cohorts table, cohort details, OMC)

Available in EUDC: Yes

Customers Impacted: Enabled for all customers

Description: Simply set a custom response cap to have your survey automatically unpublish after reaching the desired number of responses.

Why: Reduces Admin management load while also annoying a lot fewer users.

Available in EUDC: Yes

When: Available now

Description: Trigger a callback function defined in your Guides and Surveys instrumentation with a button action. Use the Run Callback action to execute your callback on a guide or survey button click.

Why: Customers sometimes want a guide to perform a custom action that they can’t reproduce with our existing button actions. It’s also likely they already have this action defined in their own application. Callback actions can fill in the functionality that isn’t provided by link or click actions.

Available in EUDC: Yes

Customers: Enabled for all customers by default

When: Available now

Description: We’ve redesigned the overlay editing experience with a toolbar for quick actions and a drawer for detailed editing. The drawer supports several new CSS style properties that can be easily edited in the UI, as well as a CSS editor to directly write CSS to be applied inline for our more experienced users.

Where: Web experiment overlay

Available in EUDC: Yes

When: Now

Description: Adds the ability to copy a guide, survey, or theme across projects!

Why: Many customers use projects to manage environments and need an easy way to copy guides, surveys, or themes across projects without re-creating and manually syncing changes.

Customers: This functionality is gated to Enterprise customers.

Available in EUDC: Yes

When: Available from May 8th.

Description: Customers can now add categories to custom and labeled events, enabling them to organize them like any other precisely tracked event. Custom and labeled events will show up under their respective categories in event dropdowns, and Amplitude Data supports filtering and sorting on this new metadata to help with management. When creating new labeled events, customers can also categorize directly from the visual labeling experience.

Why: Customers want to categorize their custom and labeled events to help with organization and discoverability, just like other events in their taxonomy.

Available in EUDC: Yes

When: Now!

Description: Localization lets customers configure supported languages and then set up translations for these languages for every guide or survey. Translations can be set up by uploading XLIFF files or by directly editing in the Guides and Surveys builder UI.

Why: Customers with applications that support different languages naturally want to display guides and surveys in the correct language. Our previous solution, creating a separate guide for each language, is very messy and has many shortcomings.

Customers: Multiple large customers have been waiting for this.

Available in EUDC: Yes

When: April 29th, available for everyone

Useful Resources: Documentation

Description: Quality of life enhancements to the Test and Preview modal for Web Experimentation. Customers can now more easily preview multiple variants and share the preview links with others to validate their experiment.

Why: Reduce the number of clicks customers need to make to preview their experiment.

Description: This update splits up the code for the Guides and Surveys SDK into small chunks. This way, users only load the pieces they need. On an internal test, we downloaded ~15% less Guides and Surveys code! ⚡

Why: Some customers are very picky about bundle size. Given how many features Guides and Surveys offers, our SDK is on the larger side. Splitting means that customers won’t load code for products they aren’t using, and will load less code overall.

Available in EUDC: Yes

Customers: Enabled for all customers by default

When: Live since April 28

Description: Introducing a beautiful new metrics library with an entry point in the left-nav, a detailed metrics page where you can explore the metric with a visualization and rich metadata, and easy access to experiment workflows :test_tube: :chart_with_upwards_trend:

Why: Our customers measure the growth of their business through metrics (though they can go by many names, like OKRs or KPIs). But today, these core metrics are either hidden away in the OMC, saved as charts and lost in a sea of content, or used in experiment but disconnected from the rest of the platform. With this release, customers can now better define, manage and take action on their their metrics using full platform capabilities.

• For the analyst/PM/marketer we have a consumer-friendly experience for viewing and exploring metrics with key property breakdowns. Actions like experimentation are front-and-center
• For the data admin, we have long-awaited governance functionality like detailed history logs and rich, sortable "used by" metadata on every metric

Description: Time to Live (TTL) gives customers control over how long event data is retained in their Amplitude instance. With TTL, customers can set a custom retention period at the project OR organization level, ensuring that only relevant data is stored to manage compliance. Once TTL is enabled, Amplitude will automatically delete event data older than your specified retention period.

Why: Companies implement data retention policies to comply with legal and regulatory requirements, ensuring they store and delete data according to industry standards. These policies help reduce security and privacy risks by limiting unnecessary data exposure. For conglomerates with different business units, we’ve built project level support to enable them to have distinct TTL policies to match each unit’s terms of service. Additionally, adoption of TTL will reduce Amplitude’s COGS by not storing data longer than needed.

Where: Admins on Enterprise orgs can turn on TTL from Organization Settings

Available in EUDC: Yes

When: Now! Customers on the prior version of organization TTL have been migrated to this new version—no action is required on their side.

Customers Impacted: TONS of customers have requested these features for years.

Useful Resources: See documentation on Time-to-Live settings.

Description: Customers can now set Visibility on Events and Properties, and also remove ownership on Events and Property Groups through CSV Import/Export.

Why: Enterprise customers leverage CSV Import/Export to automate bulk updating their data management processes and align their taxonomies with existing systems. Previously, CSV Import/Export did not support setting visibility on events and/or properties, preventing customers from automating which events and properties their users can see in Amplitude. This capability matches functionality in our UI and is another step to helping customers manage their data at scale. We now also fully support managing ownership of Events and Property Groups through this functionality.

Where: In Data under the Events and User Properties sections.

Useful Resources: CSV Import/Export

Description: We’re excited to announce a feature extension of Cohort Sync Webhook which supports triggering campaigns in tools like Braze whenever a user enters or exits a cohort. The integration now supports up to 50 user properties alongside the user ID to personalize campaigns and enrich downstream data.

Customers can select which user properties to include through a new self-serve UI and reference them directly in their templates. Previously, the webhook only forwarded user IDs, limiting flexibility for destinations like Braze. With this improvement, customers can build high-intent, time-sensitive campaigns, such as cart abandonment, more efficiently.

Why: With this webhook, Amplitude sends cohort entry and exit events directly to Braze when a user enters or exits a cohort. This provides event triggered updates easier to use and more efficient for customers.

When: Available to all customers.

Description: A common trigger type for guides and survey is On event tracked. We have had this since launch, but only now you can limit the trigger to events that have certain properties. It also works for checklist goal completion (Event is tracked).

Why: Triggering on any event of a certain type is rarely what customers want to do. Being able to filter on event properties provides you with lots of triggering options out of the box.

Customers: We believe this is a great feature addition for anyone using Guides and Surveys.

When: Available for all Guides and Surveys customers

Description: A simple, no-code method for triggering a guide or survey when clicking an element

Why: Triggering a guide or survey on element click required instrumenting your app to track an event or call our SDK. The "when element is clicked" trigger enables you to visually select the element in your application with our click selector.

When: Available for all Guides and Surveys customers

Description: "I love downloading giant files of literally every user property that's ever existed when I download my cohort as a CSV!", said no one ever. That's why we're not doing that anymore (unless you want to). With this feature, you can now download your favorite user properties that you love looking at in the preview table!

Why: This feature allows for faster downloads due to smaller file sizes, quicker insights with targeted user properties (instead of scrolling for days), and more use cases for the preview table that already exists on the cohort details page.

Where: On the "Export CSV" button in the cohorts toolbar within the cohorts details page.

When: Feature is already enabled for all customers

Description We’re officially GA'ing the new Journeys chart, a consolidation of the previously separate Pathfinder, Pathfinder Users, and Legacy Journeys visualizations into a single, powerful chart experience.

Over the years, Amplitude has had eight different tools to help customers understand user paths, which made it confusing for customers not knowing where to start. This release dramatically simplifies the experience while maintaining the feature capabilities.

As part of the GA, we made the following improvements:

• Funnels to Journeys transition.
• Journeys is a complex chart and some customers could experience latency. We added pruning here to improve performance.
• Deprecation of Top User Paths and legacy Journeys charts.

Why With our previous approach, customers told us they struggled to:

1. Understand how actual customer behavior deviates from their ideal journeys.
2. Explore journeys progressively—from high-level patterns to user-level examples.

This release addresses both by:

• Merging three charts into one consistent entry point
• Helping customers compare drop-offs in Funnels with actual behavior in Journeys (having more consistent, 1 to 1 results)
• Improving discoverability and reducing tool overload

When: Live now for all customers

Description: Amplitude’s Heatmapping feature builds on our current Session Replay providing customers with a visual, macro-level view of user engagement. It highlights where users are clicking, scrolling, and engaging most on site or app, helping teams uncover behavioral patterns and trends to make data-driven decisions that enhance product design, content placement, and overall user experience. It automatically generates up to 10 default heatmaps for the highest-traffic pages (currently available for Corp Site 2.0 and Amplitude 2.0, with broader availability coming soon). Mobile heatmaps for iOS, Android, and Flutter are planned but not yet available.

Availability: Heatmaps are available to customers on Growth and Enterprise plans who have the Session Replay addon.

Why: Heatmapping is table stakes for qualitative insights. Product managers, designers, and marketers need to be able to see where users click, scroll, and drop off.

Useful Resources: Help documentation

Description: Enables users to reposition elements on a web page as part of an experiment. This feature is available as a new control in the visual experiment editor's edit widget.

Why: Allows for testing layout changes and their impact on user behavior without requiring code changes. This capability is essential for running web experiments as it provides a flexible, non-technical way to test how different element positions affect user engagement, conversion rates, and overall page performance.

Useful Resources: Amplitude Docs – Move Elements in Web Experiment

When: Available as of 2/27/2025

Description: The Visual Editor for Web Experiment has been updated with a new design! We’ve also heard from users they want to preview the visual changes to their site in different device sizes. The new Visual Editor is responsive and supports small viewports. This improves the experience if customers want to resize their browser or leverage the browser’s device sizing feature to preview their site.

Where: Web Experiment Visual Editor

When: Available now

Description: We have introduced a new Cohort Sync Modal to connect cohorts with other products, including Charts, Experiments, Guides, and Surveys. This enhancement helps drive Cohort Usage across products across the platform.

Why: By integrating cohorts more easily across the platform, all customers benefit from a better experience and higher retention for cohorts.

When: Available Now

Description: Customers can now create web experiments directly from the Marketing Hub.

Why: Makes it easier and faster for Marketers and Growth teams to identify an area to optimize and build an experiment to improve performance from one place.

Where: Marketing Hub -> Page Engagement, only when grouped by a URL.

When: Today

Description: • You can now target web experiments on Amplitude user properties and cohorts. • We automatically update your web experiment's evaluation mode and have a new Anti-flicker setting when the web experiment is using remotely evaluated targeting or bucketing.

Why: Teams can now easily target key segments based on behavior to drive more personalized web experiences. This differentiates Amplitude Web Experiment from other web experimentation platforms.

Where: Web Experiment -> Targeting -> Update your targeting with remote user properties and cohorts

When: This is GA now! This feature is available for Web Experiment Growth+ customers.

Useful Resources: Help doc

Description: Enables users to seamlessly navigate through multiple pages within the visual editor, enhancing their ability to set up and modify experiments for key flows on their website.

Why: Web experiments often involve multiple pages, but making changes was challenging because the visual editor only supported single-page editing. This enhancement is one of the most requested features from our customers, designed to make multi-page experiment setup more intuitive and efficient.

Where: Visual Experiment Editor

When: GA today

Useful Resources: Help doc

Description: Customers can now utilize Propcount in Experiment in addition to Analytics. This is only supported for numeric event properties. A common use case is to count the number of days a user has performed an action.

Why: Provides customers more flexibility for Experiment use cases and more consistency across the Platform.

Where: This is available in formula metrics for Feature Experiment, Web Experiment, and Experiment Results.

Description: Visually edit, add custom code, or split traffic to different URLs with a new product: Amplitude Web Experiment. Customers can create experiments with a no-code visual editor and start running A/B tests faster and more easily.

Amplitude Web Experiment GA Features include: • Visual Experiment Editor • Audience Targeting • Page Targeting • Change management

Why: Growth and Marketing teams are looking for a simple, no-code way to run experiments on their websites and landing pages to drive conversion. Web Experiment is the number one requested feature for experiments.

Where: Create an Experiment > Web

Who: Available for all plans, requires an upgrade to Growth to get advanced features.

Additional Resources: Demo: https://amplitude.wistia.com/medias/sly2tuas56 Docs: https://amplitude.com/docs/web-experiment/set-up-a-web-experiment

Description: Navigate to the Individual Player page with event sync from User Streams and User Lookup.

Why: When watching a replay from User Streams or User Lookup, there was no way to get to the player page with the event stream synced unless you found the same replay on the Session Replay home page. Now you can link to the player page directly!

Where: User streams modal, Event Stream on User Profiles

When: Now!

Description: You can now restrict edit access for your flags and experiments to specific editors. Teams now also have an org-level setting to control whether new flags and experiments should default to restricted or open access.

Why: Customers want more control over who is able to modify their experiments and feature flags.

Where: Flag / Experiment > More menu > Manage Access

When: This feature is available for customers with Experiment Enterprise.

Description: Amplitude’s app with Shopify is a smart analytics app that automates eCommerce tracking. With Amplitude’s Shopify app, you can automatically track and ingest key e-commerce events, event properties, and user properties on a Shopify store. Using an Amplitude API key, customers with a Shopify or Shopify Plus store can connect their website to Amplitude in minutes to start sending events to Amplitude. Via Shopify's Web Pixel API, their order Webhooks, and our ability to inject JS on the page, we offer:

• 100% event capture for events like adds to cart, checkout steps, sales.
• Item list properties to perform cart analytics (available in Growth & Enterprise plans)
• Session replay on all pages except checkout
• Amplitude Web Experimentation
• Accurate marketing attribution via UTM parameters for page impression events (including by device & location)

Why: Customers can get set up in just a few minutes with Amplitude without needing code.

Where: The app is now available to download here: https://apps.shopify.com/amplitude

When: NOW

Description: Session Replay now supports 6, 9, and 12-month retention timeframes.

Why: Historically Session Replay has only supported 1 month (OOTB) and 3 month retention (via add-on purchase) periods for replays.

Where: Currently managed internally through DynConf.

Description: See event details/properties in the session replay event stream.

Why: While watching a session replay, you might want to see the details and properties of the events that are firing, but previously you would have to go to the user timeline and find the event again. Now you can view it directly!

Where: When viewing an individual session replay, you can now expand an event.

When: Now!

Description: Search for events in the session replay event stream.

Why: Oftentimes, customers reach a session replay in the context of an event, but it can be hard to find exactly where in the replay that event happened. Now they can easily search for the event and watch from there!

Where: When viewing an individual session replay, there is now a search box in the event stream.

When: Available now

Description: We have made improvements to the experiment configuration for setting up experiment goals and choosing metrics. Users can now set goals for experiments using new metric goal types, allowing for individual analysis of each metric. Additionally, we are relaxing the requirement to set a “primary” metric by offering users the option to opt out of the recommendation features.

Why: Users are forced to use at least one, but also only one primary metric in order to define their goals in Experiment. The current state can block teams that want to track many metrics as a measure of success.

This update is designed to relax that requirement so that customers can have either zero or multiple primary metrics, and its implications on recommendations, notifications, and duration estimation. The main goal is related to customer health and adoption - experiments that do not leverage metrics are basically just feature flags, so giving customers more ways to feel comfortable adding metrics is critical as a prerequisite for delivering value with our product.

When: GA on Monday, August 5th.

Description: Experiment now supports propmin and propmax for Feature Experiment, Web Experiment, and Experiment Results.

Why: This provides customers more consistency when interacting with metrics in both Analytics and Experimentation products.

Where: Feature Experiment, Web Experiment, and Experiment Results

Description: We revamped the "Skip Inactivity" functionality in our Session Replay Player to improve the overall user experience when navigating through long periods of inactivity.

Why: When users have long session replays, there tend to be extremely long gaps in between playable periods with event activity, which causes the replay to become very hard to interact with. We have changed the progress bar visualization to condense these inactive periods to a minimum, so users can focus on important portions of the replay and get insights more easily!

Where: Anywhere with the session replay player

Description: A one-line integration between Segment and Session Replay.

Why: Previously, we provided copy/pasteable documentation on how to integrate Session Replay with Segment through our Standalone SDK. Customers often ran into issues attempting to implement the code themselves. Now, customers can add a single line of code to their codebase to leverage Session Replay with their Amplitude events sent via Segment.

Where: Documentation for installation and usage can be found here: https://amplitude.com/docs/session-replay/session-replay-wrapper-for-segment

When: Available now!

Description: • Flags and experiments can be now configured with Prerequisite Flags and Experiments. • Evaluation of a given flag/experiment can be dependent on the evaluation of other flags/experiments for use cases including release groups or running sub experiments.

Why: Dependent feature flags and experiments is a staple of robust feature flagging platforms. Creating dependencies increases the flexibility of your feature flagging platform, unlocks advanced use cases, and enables customers to effectively scale feature delivery and experimentation across multiple teams.

Where: The Dependencies card is below the Overview card for experiments and below the Settings card for flags.

When: • GA June 26 • This feature is only available for Feature Experiment Enterprise plans

Description: We are pleased to announce the addition of a new privacy config section in the Session Replay Admin UI. This update enables users to modify the masking level and create custom masking rules using CSS selectors directly via the UI. Along with this feature, we are also updating our SDK versions to support these configurations. We’ll be releasing to all plans with session replay access over this week.

Why: This feature will help customers more easily set up their Session Replay privacy settings to configure masking levels and masking rules to adhere to their business needs.

Where: New Session Replay Settings page under Organization Settings

Description: The analysis table in Experiment and Experiment Results is getting a redesign to make it easier to read and identify significant variants. Metrics are structured as rows, while variants are displayed across columns. Table cells can be hovered to bring up a card with details, and are now colored if that variant is statistically significant.

When: Live Now

Description: We’ve implemented a Session Replay Admin UI allowing users to modify their project level sample rates via the UI (as historically they could only update it via the SDK). We’re also bumping our SDK versions with this release. The Admin UI will be available for Starter_v3 and Plus_v3 orgs with this release, and then it will be made available to all others.

Why: This feature will help customers more easily set up their Session Replay settings to configure some settings they currently need engineering support to do via SDK.

Where: New Session Replay Settings page under Organization Settings

Description: We’ve implemented a session duration filter on the Session Replay search page that allows users to filter out the session replays based on the duration.

Why: This feature will help customers locate the session replays with a given session duration easily.

Where: Session Replays Search page

Description: We’ve implemented a copy link button when you view Session Replays in charts that allows users to copy the link of a given session replay and links to the standalone session replay page.

Why: This feature will help customers share the session replays with others easily while they exploring the session replays on user steam/event stream.

Where: Event Seg, Funnel, User Sessions, Journeys Charts

Description: A default deployment is just the analytics Project API Key, now usable with all experiments and flags! Default deployments aim to help solve the problem that new customers must create a deployment before successfully implementing an experiment and delivering flags and experiments to their applications. Deployment keys also increase the burden of key management on developers, and default deployments help reduce this burden.

Where: Experiment users can now select the Project API Key as a deployment for feature flags and experiments within a project. The Project API Key is the same key used to initialize Analytics SDKs or authenticate requests to event ingestion APIs.

When: Now!

Description: Customers who use the NodeJS server-side SDK can now listen for flag config updates and receive them generally within 1 second instead of continuously polling for flag config changes.

Why: Currently, customers’ servers have to keep polling at an interval to receive the newest set of flags.

Now, we can push updates to the SDK and customers’ servers can serve the freshest flag configs right after they make changes in Experiment. They are able to perform use cases such as a kill switch to stop or modify an experiment instantly.

Where: In Node JS server side Experiment SDK. Requires opting in using streamUpdates configuration.

Useful Resources: https://www.docs.developers.amplitude.com/experiment/sdks/nodejs-sdk/#initialize-local

Description: We have released an updated version of the SDK that improves the consistency of synchronizing state between Browser SDK and the Session Replay plugin. This also includes other improvements such as removing the need for Session Start/End events for Session Replay plugin, and a debug mode to help with debugging local development.

Why: This feature will help resolve instrumentation issues that customers have run into during onboarding.

Where: This feature and its documentation can be found at the Session Replay Developer Docs.

Description: We’ve implemented persisted filtering on the Session Replay search page that allows users to share their filtered results with others. All time range and other filters will now reflect in the URL!

Why: This feature will help customers share their filtered session replay searches easily with others by sharing the link with persisted filtering search parameters. This will also unlock other session replay features for Governance and CDP teams.

Where: Session Replays Search page

Example: Amplidemo search filter! https://app.amplitude.com/analytics/amplidemo/session-replay?filters=[{%22type%22:%22event%22,%22countFilter%22:{%22group_type%22:%22User%22,%22subprop_key%22:%22count%22,%22subprop_op%22:%22greater%20or%20equal%22,%22subprop_type%22:%22event%22,%22subprop_value%22:[%221%22]},%22eventType%22:%22Add%20to%20Cart%22,%22eventFilters%22:[]}]

Description: We want to allow customers to test mutual or holdout groups by specifying either individual or cohort inclusions. Updated documentation and screenshots are available here (Set up and run mutually exclusive experiments) or here (Exclude users from your experiments with holdout groups)

Customers Impacted: Feature Experiment Enterprise customers

Description: Customers can now collapse option groups in property dropdowns and split Experiment User Properties into their own group.

Customers also have a new “Copy Selected” button in property value drop-downs, so to copy a filter or segment, you just hit that button, paste the values into another segment or filter, and click “Select All!”

Why: Makes using Amplitude faster and easier for organizations with large numbers of properties and property values.

Where: Wherever you can select Properties and Property Values! Analytics, Experiment, Data... you name it.

When: The Copy Selected feature is available in all dropdowns that have a “Selected” section. The collapsible property option groups are available in the new chart controls and anywhere using newer property dropdowns.

Description: Customers are now able to query the Management API to list all versions of all flags and experiments across all projects that your API Key has access to, with pagination and filtering by start and end time. This allows customers to retrieve a list of all changes with a single endpoint.

Why: This endpoint allows customers to retrieve a list of all changes for various use cases like debugging, auditing, or to troubleshoot what could have caused an incident. This enables customers to go through changes much faster.

Where: Using Management API, users can query the endpoint described in the dev docs.

Description: We’ve implemented a Session Replay Ingestion Monitor page that tracks Session Replay status over time. The Ingestion Monitor displays charts that show the count of the following status over a time range that users select: Successful request (status 200), Throttling errors (status 429), Quota exceeded errors (status 402) and Invalid session IDs. Additionally, we have enhanced the clarity of the Session Replay error messages that users see when trying to view a session replay that has an issue.

Why: This feature will help customers self-serve debug issues with their Session Replay implementation and provide extra clarity to customers when they encounter an error while viewing a replay.

Where: Ingestion Monitor: The top-right of the Session Replay section of your project’s Users & Sessions tab.

Description: We want to simplify customers’ workflow when they are adding a long list of users in testing. It is now possible to test your experiment by specifying a cohort as well. Cohorts are available in the testers’ section of the app.

Customers Impacted: All Experiment customers.

Available From: January 29, 2024.

Description: We've implemented the ability to add a session replay to dashboards and notebooks from any place a session replay can be viewed. Users are also able to use the core dashboard/notebook features as well, such as copy notebook/copy dashboard. Note this is one-way (you can't add a session replay while on a dashboard/notebook yet).

Why: This feature helps customers tell stories and innovate faster. It makes it easier for colleagues to understand insights uncovered so customers can get buy-in on their product recommendations.

Where: Accessible anywhere the Session Replay component lives (SR Search Page, User Streams, User Look-Up, etc).

Description: We've implemented a new session replay page where you can see and interact with Amplitude events associated to the replay and also view relevant metadata. The new page also features auto-scrolling, so the user can match the Amplitude events to replay events in real-time and jump to a precise moment of the replay when selecting an event.

Why: Help customers actually understand the parts of the product their customers are engaging with and learn where they have instrumentation opportunities with the event stream. With this enhancement, the power of Amplitude's event-based analytics really shines relative to the session replay competition (whose comparable "event stream" is a list of CSS selectors based on auto-track).

Where: Accessible through the SR widget on the Amplitude homepage, and the new SR search home page under Users & Sessions. We plan to introduce this into the chart experience as well.

Features: • Auto-scroll in sync with player. • Pause auto-scroll with event list interaction (scroll, click). • Highlight current event within player. • Jump to selected event.

Available in EUDC: Yes