Releasesby GlyphNetwork Request and Frustration Interaction Tracking
Enables/disables capturing network request events invoked by XHR and Fetch . If true , Amplitude tracks failed network requests. To configure what gets captured, set this as a network tracking options object. Default value is false . See Track network interactions for more information and configuration options.
Also shipped Nov 21, 2025Amplitude in November 2025 →
Dataflow now supports speculative execution for batch pipelines
Dataflow now supports speculative execution for batch pipelines. This feature mitigates the impact of slow-running tasks ( stragglers ) by launching a redundant execution of these tasks. The first task to finish is used, and the other is canceled, which can improve the overall completion time of your pipeline. This feature is generally available.
What's new in Sigma
Admin Add a key file for Snowflake key pair connections When configuring a Snowflake connection, you can add a PKCS#8-formatted key file ( .p8 ) instead of pasting your private key when setting up key pair authentication for the connection or an OAuth service account. For more details, see Connect to Snowflake .
Containers - New CPU Pricing for Containers and Sandboxes
Containers and Sandboxes pricing for CPU time is now based on active usage only, instead of provisioned resources. This means that you now pay less for Containers and Sandboxes. An Example Before and After Imagine running the standard-2 instance type for one hour, which can use up to 1 vCPU, but on average you use only 20% of your CPU capacity.
Notifications, Conductor Queue
This week is all about staying ahead of issues: Notifications graduate from Priority Boarding to General Availability, giving everyone a real-time view of what’s happening across projects and environments. There’s also a new way for our community Conductors to triage questions faster.
Projects deployed using a zip file via API now support branch deploys
When you deploy a project using a ZIP file and the Netlify API, you can now also create branch deploys using the new branch parameter. While it was always possible to pass a branch parameter to the https://api.netlify.com/api/v1/sites/{site_id}/builds endpoint, it previously had no effect for deploys made programmatically using the API.
Faro Web SDK v2.0 is now GA
This major release brings new updates to User Actions for GA, introduces improvements to Web Vitals, simplifies configuration, cleans up deprecated internals, and adds experimental navigation instrumentation for soft navigations. Highlights: User Actions are now GA Additional configuration to manage action state Added an importance attribute (e.g.
More from AmplitudeEvery Amplitude release →
Debug Guides and Surveys with the Amp Chrome Extension
Description: • Quick access to verify SDK Setup • Troubleshoot guides and surveys or Preview one directly • View user properties • View all forwarded events or send a test event to trigger a g/s Why: Knowing and running JS console commands is a hurdle for customers who need visibility into G/S setup.
Data Assistant: Automated Tasks
What it is: Automated Tasks in Data Assistant lets customers define and schedule data governance workflows that run without manual intervention. Once a rule is configured, the system enforces it continuously.
TRC General Availability
The TRC feature has been generally available (GA) and is on for all applicable organizations.
AI Feedback
Description: Amplitude’s AI Feedback is the new way to listen to users at scale. It helps you understand what customers are saying and why it matters. It uses AI to analyze reviews, surveys, and user feedback at scale, turning unstructured language into clear insights about customer needs and product opportunities.
Conditional Logic V2 (now with user properties)
Description: Personalize guides and surveys with conditional actions or branching paths based on user properties. Why: Bring conditional logic to guides (previously surveys only) Personalization → higher engagement: Customers can tailor the guide or survey flow to different user segments based on who the user is (e.g., free vs.
Labeled Events in Custom Events
Description: Labeled events can now be used in custom events as well as inline custom events on charts. Why: As part of the continued push for autotrack, labeled events deserve to be more of a first class citizen in Amplitude - customers aren't going to understand the nuance that a labeled event is a custom event "under the hood".
SESSIONTOTALS now works in Event Segmentation
Description: You can now use SESSIONTOTALS(event) to count how many sessions include a given event or in a metric. Small update, big quality-of-life win. :tada: Why: Streamlines using sessions in the Events Segmentation chart. No longer need to switch charts to count sessions! Where: Event segmentation formulas.
Autocapture: Page Properties
Description: Autocapture will now include new page properties consistently across both all Autocapture events and precisely-tracked events, adding more ways to filter analyses just by using the latest Browser SDK.