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

New INI setting to specify the number of rows to archive in Behavior > Site Search #14087

Open
mattab opened this Issue Feb 11, 2019 · 0 comments

Comments

Projects
None yet
2 participants
@mattab
Copy link
Member

mattab commented Feb 11, 2019

The Site Search Keywords reports are so valuable because they show what people are thinking about when browsing (and searching) for content on the website.

The reports are limited to 500 rows by default.

The goal of this issue is to let users specify a higher limit (eg. 3000 or 10000) so that Matomo will keep the top 10,000 internal search engines keywords each day/week/month/year.

Currently the following INI settings are available:

; maximum number of rows for any of the Actions tables (pages, downloads, outlinks)
datatable_archiving_maximum_rows_actions = 500
; maximum number of rows for pages in categories (sub pages, when clicking on the + for a page category)
; note: should not exceed the display limit in Piwik\Actions\Controller::ACTIONS_REPORT_ROWS_DISPLAY
; because each subdirectory doesn't have paging at the bottom, so all data should be displayed if possible.
datatable_archiving_maximum_rows_subtable_actions = 100

; maximum number of rows for any of the Events tables (Categories, Actions, Names)
datatable_archiving_maximum_rows_events = 500
; maximum number of rows for sub-tables of the Events tables (eg. for the subtables Categories>Actions or Categories>Names).
datatable_archiving_maximum_rows_subtable_events = 500

So we have available this datatable_archiving_maximum_rows_actions but changing it will also affect other reports in Behavior menu (and use lots more disk space, CPU, etc.).

-> by adding a new datatable_archiving_maximum_rows_site_search then we could up the limit for the Site Search report only and save cost/performance.

@mattab mattab added the Enhancement label Feb 11, 2019

@mattab mattab added this to the 3.9.0 milestone Feb 11, 2019

@katebutler katebutler self-assigned this Feb 13, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment