Checkpoint

Author: HeidiSteen

articles/search/search-traffic-analytics.md

@@ -1,5 +1,5 @@
 ---
-title: Collect search traffic telemetry data
+title: Search traffic telemetry data
 titleSuffix: Azure Cognitive Search
 description: Enable search traffic analytics for Azure Cognitive Search, collect telemetry and user-initiated events using Application Insights, and then analyze findings in a Power BI report.
 
@@ -9,37 +9,38 @@ ms.author: heidist
 
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 12/20/2019
+ms.date: 03/18/2020
 ---
 
-# Collect search traffic telemety data in Azure Cognitive Search
+# Collect telemetry data for search traffic analytics
 
-Search traffic analytics is a pattern for implementing a feedback loop for your search service. The objective is to collect telemetry on user-initiated click events and keyboard inputs. Using this information, you can determine the effectiveness of your search solution, including popular search terms, clickthrough rate, and which query inputs yield zero results.
+Search traffic analytics is a pattern for implementing a feedback loop for your Azure Cognitive Search service. The objective is to collect telemetry on user-initiated click events and keyboard inputs. Using this information, you can determine the effectiveness of your search solution, including popular search terms, clickthrough rate, and which query inputs yield zero results.
 
 This pattern takes a dependency on [Application Insights](https://docs.microsoft.com/azure/azure-monitor/app/app-insights-overview) (a feature of [Azure Monitor](https://docs.microsoft.com/azure/azure-monitor/)) to collect user data. You will also need to add instrumentation to your client code, as described in this article. Finally, you will need a reporting mechanism to analyze the data. We recommend Power BI but you can use any tool that connects to Application Insights.
 
 > [!NOTE]
-> The pattern described in this article is for advanced scenarios and clickstream data generated by your client. Alternatively, you can report on log information generated by your search service. For more information about service log reports, see [Monitor resource consumption and query activity](search-monitor-usage.md).
+> The pattern described in this article is for advanced scenarios and clickstream data generated by your client. Alternatively, you can report on log information generated by your search service. For more information about service log reports, see [Collect and analyze log data](search-monitor-logs.md).
 
 ## Identify relevant search data
 
-To have useful search metrics, it's necessary to log some signals from the users of the search application. These signals signify content that users are interested in and that they consider relevant to their needs.
+To have useful search metrics, it's necessary to log some signals from the users of the search application. These signals signify content that users are interested in and that they consider relevant.
 
-There are two signals Search Traffic Analytics needs:
+Two signals are needed for search traffic analytics:
 
 + User-generated search events: only search queries initiated by a user are interesting. Search requests used to populate facets, additional content or any internal information, are not important and they skew and bias your results.
 
 + User-generated click events: By clicks in this document, we refer to a user selecting a particular search result returned from a search query. A click generally means that a document is a relevant result for a specific search query.
 
-By linking search and click events with a correlation ID, it's possible to analyze the behaviors of users on your application. These search insights are impossible to obtain with only search traffic logs.
+By linking search and click events with a correlation ID, you'll gain more insights into how your application performing.
 
 ## Add search traffic analytics
 
-The signals mentioned in the preceding section must be gathered from the search application as the user interacts with it. Application Insights is an extensible monitoring solution, available for multiple platforms, with flexible instrumentation options. Usage of Application Insights lets you take advantage of the Power BI search reports created by Azure Cognitive Search to make the analysis of data easier.
+The signals mentioned in the preceding section must be gathered from the search application as the user interacts with it.
+ Application Insights is an extensible monitoring solution, available for multiple platforms, with flexible instrumentation options. Usage of Application Insights lets you take advantage of the Power BI search reports created by Azure Cognitive Search to make the analysis of data easier.
 
 In the [portal](https://portal.azure.com) page for your Azure Cognitive Search service, the Search Traffic Analytics page contains a cheat sheet for following this telemetry pattern. You can also select or create an Application Insights resource, and see the necessary data, all in one place.
 
-![Search Traffic Analytics instructions][1]
+![Search Traffic Analytics page in the portal](media/search-traffic-analytics/azuresearch-trafficanalytics.png "Search Traffic Analytics page in the portal")
 
 ## 1 - Select a resource
 
@@ -164,10 +165,10 @@ Every time that a user clicks on a document, that's a signal that must be logged
 *JavaScript*
 
     appInsights.trackEvent("Click", {
-    	SearchServiceName: <service name>,
-    	SearchId: <search id>,
-    	ClickedDocId: <clicked document id>,
-    	Rank: <clicked document position>
+        SearchServiceName: <service name>,
+        SearchId: <search id>,
+        ClickedDocId: <clicked document id>,
+        Rank: <clicked document position>
     });
 
 ## 3 - Analyze in Power BI