Active
Project:
Apache Solr Statistics
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
9 Sep 2009 at 19:35 UTC
Updated:
4 Jan 2010 at 21:37 UTC
Jump to comment: Most recent file
Comments
Comment #1
janusman commented#1: Report on facet usage: committed this patch. This now distinguishes the different vocabularies a term might have come from.
Comment #2
janusman commentedScreenshot illustrating the above patch's result.
Comment #3
janusman commentedFor #2: "clickthru" or other "conversion" tracking:
Node view/edit/delete:
a) modify the link to each result using the hook_apachesolr_preprocess_result(), then check for it in a hook_nodeapi()
Pros: exact. Cons: overridable by each theme's implementation
b) write out a cookie with each search and node-view that auto-increments, write it to the logfile. Only relate node view/edit/delete if they come directly after the last search done.
Pros: easier. Cons: exact? I figure this is how Google Analytics does it =)
c) Just log node views to our table and assume any node view/edit/delete actions with the previous search.
Pros: easiest. Cons: making assumptions, not as exact.
I need to research =)
For other tracking other "conversions" (node flagging, forwarding, etc) it would maybe be the same as above but using their own hooks instead of hook_nodeapi().
Some sample cases:
How would I say a "flag" conversion occurred after a search in these two scenarios?
1) search -> view node -> flag node
4) search -> 1 hour passes -> view node -> flag node
2) search -> view node -> edit node -> view node -> flag node
3) search -> view node1 -> edit node1 -> back to results-> view node2 -> flag node2
Would I still say a search resulted in flagging in each?
Comment #4
robertdouglass commentedPatch doesn't apply? The graphs look very nice.
Comment #5
janusman commentedActually, that patch was committed to 6.x-1.x-dev, so you don't need to apply it =)