Chapter 3. Monitoring the system

 

This is one of the shorter chapters but still contains considerable information:

  • We’ll begin with what all data-driven applications should start with—analytics.
  • I’ll attempt to convince you of the great value of analytics, and we’ll look at how to implement an analytics dashboard.
  • I’ll introduce personas and why they’re useful.
  • Using these personas, you’ll learn different ways to represent user taste.

In the previous chapters, you learned what a recommender system produces and what you can learn from users visiting a site. At this point, you should understand what you want to achieve and what evidence you’ll need to do that. Now you’re missing only the two parts in the middle as shown in figure 3.1.

Figure 3.1. Data flow from evidence to recommendations. You start with your evidence, which you can aggregate into website usage. With that, you can start to understand the user’s tastes, which can work as input to the recommender system to produce recommendations.

To understand the two middle steps, you need to find a way to understand what your users are up to. Taking the log data that the collector described in the previous chapter, you now need to find a way to reduce the data for each user to a preference. To do this, there are scripts that auto-generate interactions, which will provide the data that I’ve based the discussion on. Then you’re going to learn about simple analytics, something that you can set up and continuously view.

3.1. Why adding a dashboard is a good idea

3.1.1. Answering “How are we doing?”

3.2. Doing the analytics

3.2.1. Web analytics

3.2.2. The basic statistics

3.2.3. Conversions

3.2.4. Analyzing the path up to conversion

3.2.5. Conversion path

3.3. Personas

3.4. MovieGEEKs dashboard

3.4.1. Auto-generating data to your log

3.4.2. Specification and design of the analytics dashboard

3.4.3. Analytics dashboard wireframe

sitemap