Skip to content
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.

Commit

Permalink
Update content/departments/data-analytics/search_analytics.md
Browse files Browse the repository at this point in the history
Co-authored-by: Peter Guy <[email protected]>
  • Loading branch information
rrhyne and peterguy authored Jan 12, 2024
1 parent b6e2b7f commit 5072bc1
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/departments/data-analytics/search_analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@
- **Definition:** Users who perform a search, then click on a result.
- **Why this metric:** When a user clicks through to a result, it signals the user found something of interest. Less obviously, a session where no results were clicked could be a sign that we surfaced the right code in the results and the user did not need to navigate elsewhere. As we seek to improve ranking, results display, and other modifications to the core workflow, tracking the impact on results clicked will help us understand how we are changing the search user experience.

- **Source of truth:** [Amplitude](https://app.amplitude.com/analytics/sourcegraph/dashboard/90h2qwld) (see: “Search result clicked and search success (all users)” chart and the middle funnel labeled "SearchRestultsClicked".)
- **Source of truth:** [Amplitude](https://app.amplitude.com/analytics/sourcegraph/dashboard/90h2qwld) (see: “Search result clicked and search success (all users)” chart and the middle funnel labeled "SearchResultClicked".)

## Search reporting tools

Expand Down

0 comments on commit 5072bc1

Please sign in to comment.