Release notes

December 9, 2019

Get instant answers via search

You can now ask questions about your Analytics data in natural language, and get quick answers to a wide range of questions. While searching for instant answers, be specific about the metric, dimension, and timeframes to get the desired response. For example, you can search for “conversions from united states last week” and see the answer in the search results. Click a search result to open the Insights panel and get more details. Learn more

NPA events and user properties

You can now mark specific events and user properties as “NPA” (non-personalized advertising signals) to signify that this data should not be used for personalized advertising purposes, while preserving measurement and content-personalization use cases. Learn more

November 14, 2019

Multiple Web Streams in App + Web properties

You can now create multiple web streams in App + Web properties (for a total of 50 streams across app and web). This release lets you measure multiple websites in the same property and distinguish them within the reporting interface. We expect this to be useful in properties where users want to analyze multiple sources of data independently. Learn more

Web-conversion export in App + Web properties

You can now export your web conversions from Google Analytics App + Web properties to Google Ads to use in reporting and bidding. Previously, this feature was only available for app conversions (Firebase). With this release we now have parity in actionability in Google Ads between app and web conversions from Google Analytics App + Web properties. Learn more

November 1, 2019

Insights

You can now see automated insights, metric changes that Analytics identifies as important to your business, and also create custom insights that are triggered by metric changes for which you set thresholds. Insights gets smarter over time as it learns about your business. Learn more

Analysis

Paths along unique nodes now allow you to perform a path analysis that displays only the changing values of your nodes.

For example, if you want to see how your users navigate through the pages on your website or screens in your app and there are multiple events tracked for each page or screen, this option within Path analysis displays only one node for each page or screen, even if the user completed many consecutive events on that page or screen. However, if the user then comes back to that page or screen after they've opened another page or screen, it will appear again as a unique node in the path. Learn more

Was this helpful?
How can we improve it?