Elasticsuite: Search analytics

[romainruaud]

Not sure about what you exactly think to do with this feature @afoucret .

Just creating it for roadmap tracking purposes.

[djenvert]

Do you have some details somewhere? In any case, it seems to me a good thing as we need more insights/analytics about what the search engines does.

[afoucret]

First we will try to develop a search usage dashboard.
The goal is to get some general insights on search usage and to target what queries require optimization.

The screen structure :

• Toolbar :
  
  
  
  • Store chooser
  
  
  • Date range picker
  
  

• Generic KPI (done) :

  • Number of searches submitted
  • Number of page views
  • Number of sessions
  • Number of sessions with a search (a bug here)
  • Searches per session
  • Number of unique visitors

• Queries list (WIP) :

  • Most popular queries
  • Popular mispelling
  • Low conversion queries (queries that have a conversion rate inferior to the avg of other queries)
  • Zero (or few) results queries

• Some graphs (TBD) :

  • Pie chart showing the proportion of mispled queries
  • Line chart showing the evolution of the number of queries (per day or per hour if a single day is selected
  • Evolution of the conversion rate of session using search compared to global conversion rate

Here is screenshot of the dev in progress :

[afoucret]

Additional note :

• All query list will have the following columns :

  • Query text
  • Store (if no store is selected in the toolbar)
  • Avg number of results over the period
  • Number of usage over the period
  • Number of unique visitors over the period
  • Conversion rate over the period

• Data are coming of our own tracker. No additional infrastructure or external service is required

[afoucret]

@djenvert , @FlorentGuilbard

What do you think of it ?
Would this make the consulting team happy ?

[djenvert]

That looks great!
I've got some questions, to discuss internally.

[romainruaud]

Please create a new branch (from master) which is embedding this module code source from our internal POC. We'll then iterate on this feature branch before the final merge on master.

[romainruaud]

implemented