Performance

TasteHit monitors a number of key performance indicators (KPIs) for you. All of them are available in the form of graphics in the Performance/Widgets section of the dashboard. These metrics are automatically collected by TasteHit, and the graphs are usually updated daily.

Overall performance of a shop

The performance of your widgets is monitored over time, so that you can see if any changes you made on your site or widget configuration affected performance positively or negatively. You can monitor the performance either collectively (all widgets at once), or individually (one graph per widget). The performance can also be displayed as raw numbers, or as ratios.

Performance monitoring

Performance can be monitored either using raw numbers, or ratios. The first graph in the performance section of the dashboard monitors the metrics of all widgets collectively. The remaining graphs monitor the metrics of invidual widgets.

For each graph, there is a menu at the bottom resembling this:

graph bottom menu

The left-most drop-down menu lets you choose between:

  • Values: This displays "raw" numbers in the graph, such as the number of times the widget has been displayed.
  • Ratios: This displays ratios of the raw numbers. For example, the number of clicks on a widget divided by the number of times the widget has been displayed. This is a useful metric because it can be interpreted as the "click rate" of the widget.
  • Per User Ratios: This is only possible for the first, collective performance, graph. It displays metrics such as the mean number of page views per visitor on your site.

The second drop-down menu displays the name of the widget whose metrics are currently being displayed, or "ALL" for the top-most, collective performace, graph.

The third drop-down menu lets you choose a time period over which you would like to display performance metrics. Options ranging from three days to two years are available.

The button at the very right lets you export the data you are currenly looking at into MS-Excel format.

Value Mode

The values monitored are the following:

  • follows: The number of times visitors followed (clicked on) a recommendation generated by TasteHit. For a specific widget, this refers to how often that widget has clicked. For the collective performance graph, this refers to clicks on all TasteHit widgets.
  • convs: Conversions. The number of add-to-carts attributable to TasteHit. We consider this to be when a visitor clicks on a recommendation, and then adds the same product to his or her cart. For a specific widget, this refers to the conversions attributable to that widget. For the collective performance graph, this refers to clicks on all TasteHit widgets.
  • displays: The number of times the widget has been displayed. If a page contains two TasteHit widgets, displaying this page will cause one "view", and two "displays". For a specific widget, this refers to how often that widget has displayed. For the collective performance graph, this refers to how often all TasteHit widgets were displayed.
  • views: The number of product pages that have been displayed. Only available for the collective performance graph.
  • carts: The number of times visitors added a product to their cart (number of add-to-carts). Only available for the collective performance graph.
  • uniqueVisitors: The number of unique visitors your site received. Only available for the collective performance graph.

Not all values are displayed in all graphs. The graphs for a single widget monitor only the displays, follows, and convs:

Monitoring performance by values

This is so because the "views", "uniqueVisitors", and "carts" are values that are global site metrics, and are not directly related to a specific widget. The collective performance graph monitors all values. Notice that the legend just below the graph ("displays, follows, convs" in the example above) is clickable. If a certain value does not appear in the graph, try clicking on the value you would like to see.

Ratio Mode

The metrics monitored are the following:

  • followsOverDisplays: The number of follows, divided by the number of displays, expressed as a percentage. For a specific widget, this can be interpreted as the click-rate of the widget: How often was a widget clicked on, compared to how often it was displayed. For the collective performance graph, this refers to the click-rate of all TasteHit widgets.
  • followsOverViews: The number of follows, divided by the number of product page views, expressed as a percentage. For a specific widget, the number of follows refers to the follows for that widget, but the number of (product page) views refers to all views on your site. For a specific widget, this can be interpreted as the percentage of all product page views that are directly attributable to that widget. For the collective performance graph, it is the percentage of all product page views attributable to all TasteHit widgets.
  • convsOverCarts: The number of conversions (add-to-carts attributable to TasteHit) divided by the total number of add-to-carts. For a specific widget, the number of conversions refers to the conversions attributable to that widget. The number of carts refers to the carts on the whole site. This can be interpreted as the percentage of all add-to-carts on your site which are attributable to that widget. For the collective performance graph, it is the percentage of all add-to-carts on your site attributable to all TasteHit widgets.

The same graph as in "Monitoring Performance Values", this time expressed as ratios, looks like this:

Monitoring performance by values

The followsOverDisplays and followsOverViews metrics are "discovery metrics": the higher these numbers, the more TasteHit is responsible for making your visitors discover product pages. The convsOverCarts metric is a "performance metric": The higher this number, the more TasteHit is responsible for add-to-carts.

When looking at graphs for specific widgets, the followsOverDisplays will often (but not always) be higher than the followsOverViews. This is because the number of displays (which is specific to a widget) will often be lower than the total number of page views on the site. For the collective performance graph, the situation will often be the reverse: the total number of displays is often higher than the total number of product page views for two reasons:

  • it is possible to have several widgets per product page, and
  • it is possible to place widgets on pages that are not product pages.

Per User Mode

For the collective performance graph, a third option, "Per User Ratios" is available. The metrics being monitored are:

  • followsPU: The average number of follows per visitor on your site.
  • cartsPU: The average number of add-to-carts per visitor on your site.
  • convsPU: The average number of conversions per visitor on your site.
  • viewsPU: The average number of (product page) views per visitor on your site.

Comments