Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Advanced Internal Site Search tracking & analytics, for internal search engines and keywords #2992

Closed
mattab opened this Issue · 18 comments

4 participants

Matthieu Aubry Timo B. Peter Boehlke Anonymous Piwik user
Matthieu Aubry
Owner

The goal of this ticket is to describe the Internal Search Tracking & Reporting feature for Piwik core.

Currently, a third party built by Timo exists in #49.

We will reuse this great plugin as much as possible, integrating it into a Core plugin, maybe improving the features, user interface, documentation, and checking that it is fast & optimized on high traffic piwik servers.

More specifications and details to come later.

Matthieu Aubry
Owner

(In [7190]) Refs #2992 Site Search KABOOM, Refs #5469
Implementing Site Search tracking & reporting in Piwik core!

  • New Admin UI to customize, for each site, wheter site search is enabled. Also options to set default values to use.
  • New Reports: Searches, Searches with no result, Search categories, Top Pages Following a Search
  • to track "No result keyword" users will have to tag their site with a JS call, or add a new parameter to the search result page &search_count=X (X being zero for no result searches)
  • Reports works with Row evolution, PDF/HTML reports, Piwik Mobile
  • idaction_url is now NULLable because, Site Search records a page with idaction_name == Keyword, and idaction_url == NULL. This ensures that the Site Searches don't create "Page URL Not defined" records.
  • updates to Tracker JS API, new function trackSiteSearch, also added in PHP tracker
  • New fields in log_visit to track searches
  • new segment, "searches" which can be used to select visitors who did a search ie. searches>0 or those who searched a lot, ie searches>10

    TODO:

    • commmit integration test, TESTING, DOCS, FAQ, release, and a nice Prayer to the universe and the stars, hoping that I can code a major new feature without any bug...
    • It would be awesome to have compatiblity with Transitions so we can see, for a given site search, what are the starting pages and Destination pages

    Thank you for your patience Timo,
    and thank in advance everyone for your help Testing this new feature!

Matthieu Aubry
Owner

(In [7192]) Refs #2992 #49 Message fix

Timo B.
Collaborator

(In [7193]) refs #2992: when a keyword starts to have results (e.g. after integration result count tracking on the page), don't show it in the searches without results report anymore. (also includes a minor code simplification)

Matthieu Aubry
Owner

(In [7194]) Refs #2992 #49

  • Adding integration test
  • Note: it appears the "No result keyword" does not work, i'm on it
Timo B.
Collaborator

(In [7196]) refs #2992 preparing Site Search and Transitions integration: use idaction_url=NULL for site searches in order to identify them efficiently in Transitions

Matthieu Aubry
Owner

(In [7197]) Refs #2992 #49
Fixing the No result keyword bug

Matthieu Aubry
Owner

(In [7200]) Refs #2992 #49
Also updating schema

Timo B.
Collaborator

(In [7201]) refs #2992, refs #3332: integrating previous and following internal searches into transitions. the code is starting to get a little complicated ;-)

Peter Boehlke
Collaborator

(In [7209]) Refs #2992, added "s" and "searchword" as standard query parameters, since these are the standard search settings in wordpress and joomla. Any other CMS we should support out of the box?

Matthieu Aubry
Owner

(In [7210]) Refs #2992 #49
enable transitions for the pages following site search reports

Timo B.
Collaborator

(In [7214]) refs #2992, refs #3332 fixing two ui bugs in transitions / site search integration

Timo B.
Collaborator

(In [7215]) refs #2992: disable row evolution on site search categories because it doesn't work. TODO: make it work

Timo B.
Collaborator

(In [7216]) refs #3332, refs #2992 making transitions center box higher because new lines were added for site search. fixing a js bug when truncating urls.

Anonymous Piwik user

Replying to peterb:

(In [7209]) Refs #2992, added "s" and "searchword" as standard query parameters, since these are the standard search settings in wordpress and joomla. Any other CMS we should support out of the box?
Support TYPO3 CMS with different search engines: tx_indexedsearch[or tx_solrq or searchperience[querystring]

Matthieu Aubry
Owner
  • Tracking API document search_cat, search_count, search parameters
  • piwikTracker.setCustomUrl(document.URL + '&search_count=0');
Peter Boehlke
Collaborator

Also it would be great to support search params which were rewrited (mod_rewrite) - e.g. example.com/search/[searchword].html

Matthieu Aubry
Owner

User Manual available at: Site search analytics tracking and reporting

Peter, you could do this with some Javascript / regex and detect the keyword this way. If you do it, pleae send instructions I could add to the doc above, or in a FAQ :)

Matthieu Aubry
Owner

see follow up ticket: #3461

Matthieu Aubry mattab added this to the 1.12.x - Piwik 1.12.x milestone
Matthieu Aubry mattab self-assigned this
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.