@anonymous-matomo-user opened this Issue on February 2nd 2011

First of all, we think its import to intoduce our self. We are 3 students from Mosbach (Germany) - it`s a small town near Heidelberg. We got from our professor the business, to programing a new PlugIn for Piwik. He misses a Plugin, which could check from one possible page the InBounds and the OutBounds. We mean with InBound the pages before and with OutBound the pages after the elected page.

(We attach our first layout)

Our idea is, that the Piwik user can see on the widget the first five pages from which the people came to the elected page and where they go to. So the Piwik user can check from a page if the people goes the intended way.

On the "detail" page the Piwik user can see a Graph from this five In- and Outbounds. We think its import to visualize the result. And also the User can see the same table as on the widget, but here he could check all the In- and Outbounds (not only the first five).

Currently we stay at the beginning of this project. It`s the fist time for all of use to work in such a Open Source Community. If you have some tips or tricks for use - please let us know. You could contact us per mail: eberle-florian@web.de.

It`s also important for us to inform you about the news in our project. So you can follow our project the whole time.

If you got some questions, please do not hesitate to right us a mail!

@anonymous-matomo-user commented on February 2nd 2011

Attachment: the detailö page

@anonymous-matomo-user commented on February 2nd 2011
@robocoder commented on February 2nd 2011 Contributor

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
@mattab commented on February 3rd 2011 Member

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

@anonymous-matomo-user commented on February 3rd 2011

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.

@robocoder commented on February 3rd 2011 Contributor

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

@robocoder commented on February 5th 2011 Contributor

Moving to Feature Requests until there's code.

@mattab commented on September 17th 2011 Member

Please comment if you have some code. Thanks!

@robocoder commented on September 18th 2011 Contributor
@anonymous-matomo-user commented on September 18th 2011

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,


@mattab commented on December 14th 2012 Member

This was actually implemented as Page Transitions: #3332

Page flow / Transitions Report documentation

This Issue was closed on December 14th 2012
Powered by GitHub Issue Mirror