Opened 6 years ago

Last modified 11 hours ago

#57 new New feature

Better Data Insights. Show me what's increased and decreased, movers and shakers (beta)

Reported by: matt Owned by:
Priority: critical Milestone: 2.x - The Great Piwik 2.x Backlog
Component: Plugins Wishlist Keywords:
Cc: Sensitive: no

Description (last modified by matt)

Most popular pages/keywords/etc. are popular every day, and it is hard to know what changed since the day before. What would be interesting would be to visualize:

  • Which pages significantly increased/decreased?
  • Which URLs links/SE keywords brought me significantly more/less traffic compared to last period?

This could help answer questions such as:

  • Why did the website traffic suddenly decrease? Traffic from some Keywords/Referers significantly decreased, and some pages significantly were less seen.
  • Similar with answering "Why did traffic suddenly increase?" Why are my Ecommerce orders growing so much, how do I know the overall positive contributors explaining our growth?

User interface updates for new reports & hints

New report: Overall Movers and Shakers

This report would have to query in particular: page URL, page Titles, Keywords, websites, campaigns, maybe 8 reports, for current AND previous periods. Making 16 API calls should work fine and comparison would be pretty fast hopefully.

This report could be available as a widget showing the top 5 movers and shakers overall (increased keywords, pages, etc.).

Extend existing report: Highlight Movers and Shakers

Currently reports display "Label", "Visits count" by default. There is a button to display 5 more columns and a view for Goal conversions metrics.

We could maybe improve at least the "basic" view showing only visits.

In this view we could for example display in a new column on the right, a green or red % increase, when there is a a major change (threshold set to +/- 10% for example). Otherwise leave blank. See also #291

Extend report: Display Movers & Shakers in all reports' footer

Below the report, or above?, we could display these rows from the report that have significantly changed since yesterday.

We could put threshold of minimum visits impacted = 20
minimum % increase or decrease = 2% for example?

So it would not display minor changes that are not interesting.

They could be displayed on top of the report

*Best countries*
(green sign) India (+50%) and Scotland (+33%)
(red sign) France (-33%) and Germany (-44%)
|---------|--------|
| Country | Visits |
|---------|--------|
| India   | 176    |
| Scotland| 54     |
| France  | 23     |
| Germany | 23     |
[....]
Next >

Display evolution % next to all sparklines

Idea is to show the increase and decrease of Visits, Conversions, etc. basically next to each Sparkline. There is a proposal mockup at: http://dev.piwik.org/trac/attachment/ticket/291/sparklines.png

Implementation

To produce a report "Period VS Previous period" for each keyword, we would need to select all keywords from both periods (2 datatables), and compare both to extract significant increases/decreases.

The code would be optimized so that it returns in less than 2 seconds when calling 8 different APIs so comparing 16 datatables.

The algorithm will typically extract:

  • items with a growth of N %
  • new items (new keyword since yesterday) with at least M %
  • Never show items with less than P visits
  • By default, we should enable the display in the UI for only the very significant changes, with a high threshold of visits impacted. The feature should not bring noise if the changes are not that interesting.

New widget to show this great insights:

  • New smart widget to show what's changed in dashboard automatically based on last login date: #3250

Similar tickets

  • compare 2 periods: #291
  • show evolution for a given keyword/page: #534

Attachments (1)

2014-03-03_12h01_50.png (17.8 KB) - added by hpvd 6 weeks ago.

Download all attachments as: .zip

Change History (59)

comment:1 Changed 6 years ago by matt (mattab)

  • Description modified (diff)
  • Summary changed from Plugin to show the big moves / evolutions to Plugin to show the big moves / evolutions (increase and decrease)

comment:2 Changed 6 years ago by matt (mattab)

  • Milestone set to Future features

comment:3 Changed 6 years ago by matt (mattab)

  • Description modified (diff)

comment:4 Changed 6 years ago by matt (mattab)

  • Description modified (diff)

comment:6 Changed 5 years ago by domtop

comment:7 Changed 3 years ago by matt (mattab)

  • Description modified (diff)
  • Sensitive unset

comment:8 Changed 3 years ago by matt (mattab)

  • Summary changed from Plugin to show the big moves / evolutions (increase and decrease) to Highlight significant increases/decreases in Reports

comment:9 Changed 3 years ago by matt (mattab)

  • Description modified (diff)
  • Milestone changed from Feature requests to 1.x - Piwik 1.x
  • Summary changed from Highlight significant increases/decreases in Reports to Highlight significant increases/decreases in Reports (movers and shakers)

comment:10 Changed 3 years ago by matt (mattab)

  • Milestone changed from 1.x - Piwik 1.x to 1.7 Piwik 1.7

comment:11 Changed 3 years ago by matt (mattab)

To produce significant movers and shakers, the algorithm could maybe select "current month" dataset and compare it to yesterday if period=day, or to last week if period is week, for example to find out the items with an average very different from the number "this week" ?

See also relevant article: http://www.wired.com/magazine/2011/06/ff_feedbackloop/all/1

ALso interesting: http://www.juiceanalytics.com/writing/keyword-trends-google-analytics-greasemonkey/

    display_limit: This controls the maximum entries that each table will contain. This may be useful for large, sprawling sites.
    growth_tolerance: This is the percentage growth parameter. Changing it to .10, for example, will catch everything that has grown by 10%, as opposed to the default 50% and 20%, respectively.
    minimum_number_elements: This is a significance benchmark that can be used to limit what is displayed upon the screen. By default, only keywords with at least 10 elements are displayed upon the screen. Referring Sites does not have a minimum by default, but one can be set if desired.
    limit: Limit is more of an internal parameter that determines how many entries should be downloaded from Google in order to get the results that are visible here on the page. Lower the limit to increase speed. If the limit is set to a very high number, you will get the largest result set, but you will have to sit around for a while for the results to load. Since the results are downloaded ordered by volume, raising the limit from the default numbers will not actually give more significant results. You will simply get more of the smaller results, such as keywords with only 1 hit.
    look_back: This is a very important parameter. The script uses the date displayed upon your Google Analytics page to determine the full range that you want to consider in your results, but ’look_back’ determines how many of those days are used for the significance test. So, say the range you have displayed in Google is March 23 – April 22 and your look_back is 7 days. The script will compare the average referrals for a given keyword from April 16-22 to the average from March 23-April 15, and will return the keyword only if the recent average is 20% higher than the rest of the time period. Thus, if you want to increase the total range of the data, change the dates on the actual webpage. Change ’look_back’ only if you want to change the period of significance.

See also #3032 Trends reports

comment:12 Changed 22 months ago by matt (mattab)

  • Description modified (diff)

In general, this feature has much potential. Maybe other developers have better ideas to surface interesting data from the raw reports. We could write a simple plugin that would use the raw data to show insights. Other developers could then implement their own algorithm very easily by using the piwik APIs. We could even do a blog post and invite developers in a contest to write algorithms?

We could have a system that gives out several data insights profiles:

  • Negative/Positive Alerts when significant decreases in different categories: SEO (keywords, sites), Content (urls, downloads), Marketing (campaigns), Ecommerce (Products), Technical (Browsers, OS changes in bounce rate), Audience (returning vis, countries, mobile)
  • Display Possible actions for the users:
    • Marketing: check campaigns with visits but high bounce rate/low conversions,
    • Content: highlight high views ecommerce products with low conversion rates, highlight top viewed pages with higher than avg exit rate...
    • Technical: show significant pages with slow and/or slower than avg loading times

See also KPIs E-commerce : quels indicateurs pour votre tableau de bord for inspirations on good metrics that matter (french)

comment:13 Changed 16 months ago by matt (mattab)

  • Idea: Add new mode: color in red / orange, or green + lighter for good and bad rows. Make it a clog option. Also display, left of cog, "Enable Colors"?
  • when looking at daily reports, show best yearly items not found in daily
  • Similarly mode that compares with last month to show "New Links" or "New keywords"

see also nice ideas in http://www.kaushik.net/avinash/six-visual-digital-marketing-analytics-strategic-solutions/

Last edited 6 months ago by matt (previous) (diff)

comment:14 Changed 16 months ago by matt (mattab)

  • Priority changed from major to critical

comment:15 Changed 13 months ago by matt (mattab)

  • Milestone changed from 1.12.x - Piwik 1.12.x to 2.x - Piwik 2.x

comment:16 Changed 2 months ago by matt (mattab)

  • Milestone changed from 2.x - Piwik 2.x to 2.1 - Piwik 2.1

comment:17 Changed 2 months ago by matt (mattab)

  • Milestone changed from 2.1 - Piwik 2.1 to 2.0.4 - Piwik 2.0.4

Consolidating milestones FTW

comment:18 Changed 2 months ago by matt (mattab)

  • Priority changed from critical to major

comment:19 Changed 2 months ago by matt (mattab)

  • Milestone changed from 2.1 - Piwik 2.1 to 2.2 - Piwik 2.2

Entering 2.1 RC cycle, moving all other tickets to 2.2 milestone!

comment:20 Changed 7 weeks ago by tsteur

In 3055a6571d93272d72a5eb3201bf797577c63488:

refs #57 started to work on displaying Insights. Added a widget for the dashboard and a new Insights visualization. More to come... still early version so expect a lot of things to change but I am still happy about feedback

comment:21 Changed 6 weeks ago by matt (mattab)

In 3f2916b99967e8276ce53314d28594d630101ca5:

Enable Insights plugin for all beta testers in the coming weeks. Please send us your feedback about this new Magic Feature! refs #57

comment:22 Changed 6 weeks ago by tsteur

In b062cb7bf3086e635c39658106f1223dfd347ffd:

refs #57 added tests and fixed some bugs

comment:23 Changed 6 weeks ago by tsteur

In 7714334dee2f1f5353183867ac6f5955f121e15f:

refs #57 do not call Insights API in integration tests

comment:25 Changed 6 weeks ago by tsteur

In 8110e9db5c6589e7f426b2aec6a4f7ccb2e6146e:

refs #57 added possibility to place a widget multiple times (in case you want to see the same wdget with different visualizations and/or different parameters like different filters to make it easier comparable), removed some controls and save parameter changes in dashboard

comment:26 Changed 6 weeks ago by tsteur

In 727da1b3cbb5a7e95be430a6cce22e9b34ce5453:

refs #57 some bugfixes and started to work on insights widget

comment:28 Changed 6 weeks ago by hpvd

coool :-)

Many thanks for your work on this!!

two tiny comments for looking inside on the table sites:

  • should the filter bar stay at the bottom? At the top near to the segment-editor may be also a great place which may prevent the need for scrolling up and down when working with segment editor and insight filter at the same time...
  • same with switching between standard and insight view: bottom or top? one idea maybe something like tabs at the top so you could easily see where you are and switch between the two views...
Last edited 6 weeks ago by hpvd (previous) (diff)

comment:29 Changed 6 weeks ago by hpvd

using green and red as font colour for - and + values is great.
Maybe one could visualized the differences even more by using some kind of bars directly in the table.
Put an rough concept as attachment.

Changed 6 weeks ago by hpvd

comment:30 Changed 6 weeks ago by tsteur

In 856a3e613cf4d89efd0d4c8a7556a98632773277:

refs #57 reducing memory usage and improving performance

comment:31 Changed 6 weeks ago by tsteur

In cbe88c1ab471c717fbee06eebe556cc97c5da6e5:

refs #57 destroy all tables but the insights tables

comment:32 Changed 6 weeks ago by tsteur

In 6e022a78f6f1ac9e0b481433d6ac670dd5d5f119:

refs #57 also delete the last table

comment:33 Changed 6 weeks ago by tsteur

In 62939c122a683de27ed714f3c1af2fa84700b0ef:

refs #57 do not flatten for now, brings massive performance improvement 10min > 1 sec as Referrers_getKeywords takes forever and also leads in memory exhausted when report is flattened

comment:35 Changed 6 weeks ago by tsteur

In 23186d76e8632683f6658e42c93488ac854d65d5:

refs #57 make sure text ellipsis works and label is always only one line. moved test fixture to insights plugin as demonstration for other plugin developers as it is very insights related anyway

comment:36 Changed 6 weeks ago by tsteur

In 8601c094bd1b0e4dbf80877ea7d00ad831a1b7ba:

refs #57 some more adjustments to the widgets and added a less file

comment:37 Changed 6 weeks ago by hpvd

please see:
https://dev.piwik.org/trac/ticket/4799
"broken after update to 2.1 final"

because disabling the inside plugin fixes it...

Last edited 6 weeks ago by hpvd (previous) (diff)

comment:38 Changed 6 weeks ago by tsteur

In c25f396c2452760b9c40c95b6889a3abdfcb317e:

refs #57 started to work on movers and shakers and lots of minor improvements

comment:39 Changed 6 weeks ago by tsteur

In a9e8651ec0f0e68fb3693de3a38fb1c51351d850:

refs #57 some refactorings to have better testable code, loads of tests and bugfixes

comment:40 Changed 6 weeks ago by tsteur

In 4bb969cea4d446c230f46a41905f8a6fff4765f7:

refs #57 added more tests and some bugfixes

comment:41 Changed 6 weeks ago by tsteur

In 862e532af3672352a7f7e9eb2d763bcb0803f4e2:

refs #57 removed min impact control as it might be not clear what it is anyway and user can change the limit filter if he wants to see only entries with very high impact

comment:43 Changed 6 weeks ago by tsteur

In ad9ab5d884bab393467b4b9140e3460f99b46f8b:

refs #57 more tweaks to insights and movers and shakers and more tests

comment:44 Changed 6 weeks ago by tsteur

In 4165176308adc982bb127bb19ff8825340573f67:

refs #57 some code improvements and tests, also some adjustments for sites having not many visits

comment:45 Changed 6 weeks ago by tsteur

In fc6fe7f8ad59498061886f162375a6e75df11f66:

refs #57 make sure always a change of at least 2 visits is required. Added icon license information, will move the information later

comment:47 Changed 5 weeks ago by tsteur

In d210180a4609f8f89107e10fe8a4eafe577eaa24:

refs #57 ui tweaks and translations

comment:48 Changed 5 weeks ago by tsteur

In 81c3786bd049add8e170e1c53da32676b56c1d23:

refs #57 moving translations to general en.json

comment:49 Changed 5 weeks ago by tsteur

In 78e96146da2bb59a6a3b7a55e542be0ab353ec9c:

refs #57 average filter is no longer needed

comment:50 Changed 5 weeks ago by tsteur

In 3710bb49dc11df86f40a87c65cd1038b3bbff2db:

refs #57 some more code tweaks and documentation

comment:51 Changed 5 weeks ago by tsteur

In a4f6fc581725b21efaf079adf9fe360830247b8d:

refs #57 moved legalnotice info for insights icon

comment:52 Changed 5 weeks ago by tsteur

In e96399a840d942f8aabb387159ff9dc5d5ce4c45:

refs #57 added missing translations

comment:53 Changed 5 weeks ago by tsteur

In 2e1cb7bf6c14919a4b0f6e37e90fd72823e9c07b:

refs #57 make sure all column in overview widget have same width

comment:54 Changed 5 weeks ago by matt (mattab)

  • Milestone changed from 2.2 - Piwik 2.2 to 2.1.1 - Piwik 2.1.1

comment:55 Changed 11 days ago by matt (mattab)

  • Milestone changed from 2.2.1 - Piwik 2.2.1 to 2.x - The Great Piwik 2.x Backlog

comment:56 Changed 10 days ago by matt (mattab)

  • Priority changed from major to critical

comment:57 Changed 40 hours ago by matt (mattab)

  • Summary changed from Highlight significant increases/decreases in Reports (movers and shakers) to Better Data Insights. Show me what's increased and decreased, movers and shakers (beta)

comment:58 Changed 11 hours ago by matt (mattab)

In 9af9ae3fe1030607ccee86100089c849a8c479e6:

Refs #57 New good looking icon for data insights for Morpheus theme!

Note: See TracTickets for help on using tickets.