Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exit rate should use visits to the page, not hits #2069

Closed
mattab opened this issue Feb 5, 2011 · 1 comment
Closed

Exit rate should use visits to the page, not hits #2069

mattab opened this issue Feb 5, 2011 · 1 comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Feb 5, 2011

Reported in http://forum.piwik.org/read.php?3,71745

@mattab
Copy link
Member Author

mattab commented Feb 12, 2011

(In [3870]) Refs #1736

  • API functions returning data now have a new optional 'segment' parameter. segment can define a Visitor segment dynamically that will be applied to the report. For example, &segment=country==FR;actions>=3 (AND, OR supported. Only == and != supported currently, but easy to add more)
  • For API requests with a segment parameter, the reports will now be processed on the fly, and only the requested plugin report will be archived.
  • All plugins now define the 'segments', with a name, category, SQL field, filter, etc.
  • Simplifying archiving code a bit
  • Fixes Exit rate should use visits to the page, not hits #2069 Exit rate computation
  • New widget: lists the Top Keywords for a page URL, Widgets for a website only. Maybe later we could create a widget category "For your site"?
    • This widget is pretty cool SEO wise, but maybe the PHP snippet should do caching (not so good hitting the API on each page view... but why not?)
  • still to do!

@mattab mattab added this to the Piwik 1.2 milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

No branches or pull requests

1 participant