Attachment: the detailö page
20101113_PluginScreenshot_Detailseite.png

Attachment: the widget
20101113_PluginScreenshot_Dashboard.png

That's a very interesting project idea. I look forward to seeing the final code.

Others have asked to view click paths. So, I see some possible enhancements:

• clickable inbound and outbound urls which changes the page URL being viewed
• differentiate/toggle between internal and external urls (external referrers and outlinks)
• change the click target of Actions datatables to drill into this view

Interesting, could lead to performance issues. Would you pre-process the inboud/outbound pages for each URL on the site? Will you only keep top 10 or more?

Maybe the widget style, with the INPUT field, should be reused in the 'detail page' (best to reuse the design and be consistent in the widget and in the report). In this case, the widget could be the report without the graph. You could also have a widget with the INPUT field and just the graph.

my 2c

The plugin will show the inbound and outbound pages for a given page.

The idea of the widget is, that the piwik user can see the first five
pages which people came from and also the top 5 where they went to.

On the "detail" page the piwik user can see a graph which consists of the five In- and
Outbounds. Here you can also check all of the In- and Outbounds (not only the first five) for the given page. They will be shown in a table element.

Our first layout will be attached.

I don't think this would/should be pre-processed because the of the data size (n1 urls x (n2 inbounds + n3 outbounds)).

Moving to Feature Requests until there's code.

Please comment if you have some code. Thanks!

http://code.google.com/p/piwik-outbounds/

Hi there,

I'm one of the main developers of the outbounds-project. This ist an early Beta Version you can see following this link. We are not working on this project at the moment, because we all are working in our companies until November. After that we will meet each other again in university. We are sorry about that delay at the moment.

Let me explain how to use the beta version. You have to run a cronjob triggering runOnceADay() in OutboundsPlugin.php once a day @midnight (00***). At this point our Controllerfunction "createOptimizedTable" will be called and it will create an optimized table for the pagevisits of yesterday (optimizing the tracked pagevisits of a visitor).

Let me explain the table:

It consists of

• the date field of the db entry - containing the date ;)
• the comefrom field sais "Hey, this visitor clicked the link to page 423(="goto", see next) at page 12(="comefrom").
• the goto field sais "This visitor clicked the link to page 423".
• the count field is always initialized with '0'. Everytime the optimize function finds a user who went from page 12 to page 423 yesterday, it will say count++ where comefrom==12 and goto==423;
• the "type" entry means
  if "type" equals
  - '0' -> this dataset contains data for one day
  - '1' -> this dataset contains data for one week
  - '2' -> this dataset contains data for one month
  - '3' -> this dataset contains data for one year

But the functions to optimze weeks, months and years aren't included at the moment. But it is the same principle. To optimize a month for example, you only have to iterate through datasets with type '1' (week) and complete it with the last days in that month (type ='0').

And how 2 read optimized data?

If you want to get the top outbounds for a given page with ID "423", you have to select all data from optimized db, where comefrom == '423' DESC by count and read the goto field which countains the ID of the page you are looking for.

If you want to get the top inbounds for a given page, you have to select all data where 'goto' equals the given page ID. Now you DESC by count and you will get the top inbounds pages IDs for that page.

greetz from Germany,

Ren

This was actually implemented as Page Transitions: #3332

Page flow / Transitions Report documentation