Ticket #756 (reopened New feature)

Opened 15 months ago

Last modified 5 weeks ago

'Content detail' reporting: entry keyword and other analytics, by page

Reported by: monchito Owned by:
Priority: critical Milestone: Features requests - after Piwik 1.0
Component: Core Keywords: content detail
Cc: ramon@… Sensitive: no

Description

Just like in Google Analytics (and others) it would be great if Piwik were to support 'content detail' reports. It's basically all the reporting stuff that Piwik can do, but then for every single url of a website. Of course we could start small, and expand in a later stadium. So we could start with: entrance keywords, entrance paths, some e-commerce tracking etc. This would make Piwik much more interesting for large websites!

For now, Piwik only reports the pageviews & unique pageviews on a page by page basis, we see this when we go to site -> actions -> pages.

See  http://blog.vkistudios.com/index.cfm/2009/1/9/Google-Analytics-Power-User-Part-4-Content-Top-Content for an introduction and  http://analytics.blogspot.com/2008/06/make-your-content-reports-more-useful.html for more background info on how this looks like in Google Analytics.

I'm keeping this very general, because i have no idea how to implement this technically. I do know that it would make Piwik much more powerful :)

Attachments

mockup-piwik-content-detail_v01.pdf Download (285.1 KB) - added by monchito 7 weeks ago.
Some screenshots with inspiration

Change History

Changed 15 months ago by vipsoft

  • status changed from new to closed
  • resolution set to duplicate

Dupes:

  • Entry/exit pages #306 (see also EntryPage plugin #732)
  • Visitor path #44
  • e-Commerce (e.g., Funnel #220)

...

Changed 15 months ago by matt

  • status changed from closed to reopened
  • resolution duplicate deleted
  • summary changed from 'Content detail' reporting to 'Content detail' reporting: entry keyword by page

reopening as the request: "keyword by entry page" is a new idea, and happens to be one of the most requested feature for Piwik; we could add a query at archiving to process and report keywords for each page.

Question is:

  • how do we integrate this in the UI? How would you choose to select keyword for a given page? Ideally it should be integrated very nicely and not add any UI overhead but still being easy for the user to find out that he can show this data...

any idea?

Changed 15 months ago by monchito

For now, i would place it under 'actions' -> 'pages'. A click on a page-uri (where we now see the total/unique visits per page) would lead us to a kind of dashboard for a particular page

Changed 15 months ago by matt

  • milestone set to Features requests - after Piwik 1.0

monchito, maybe you could submit a mockup of how this could be done?

Changed 15 months ago by matt

  • summary changed from 'Content detail' reporting: entry keyword by page to 'Content detail' reporting: entry keyword and other analytics, by page

Changed 15 months ago by monchito

Hmm, i have no idea where to start to be honest... What do Piwik mockups usually look like :)

Changed 15 months ago by matt

mockups are up to you, they can be really detailed or simple; the objective is to show (specify) how the UI will work in the use cases that will have to be implemented. You can draw rough schemas with any software you like for example.

Changed 13 months ago by alivenk

Changed 13 months ago by monchito

the comment above should be deleted because its SPAM

I'm still thinking about the mockup and will respond to it when i get to it :)

Changed 5 months ago by matt

  • sensitive unset

monchito, any luck doing a mockup?

Changed 7 weeks ago by monchito

Some screenshots with inspiration

Changed 7 weeks ago by monchito

Hi, ive added an attachment with some screenshots of how this looks in Google Analytics. I think, with reagdrs to interface, we could start mimicing the way GA does it, apply the Piwik styling and we're well underway

Changed 5 weeks ago by matt

  • priority changed from major to critical

Keyword by page is a very frequent feature request.

Note: See TracTickets for help on using tickets.