Postponed
Project:
Browsing History Recommender
Version:
7.x-1.0-alpha1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
4 Jul 2009 at 03:32 UTC
Updated:
15 Jul 2011 at 13:14 UTC
Jump to comment: Most recent
Comments
Comment #1
danithaca commentedmake as "postponed" unless there's request from other users.
Comment #2
grendzy commentedI'm the maintainer of http://drupal.org/project/google_analytics_reports (which also contains the API module). I'm not sure how practical this would be - the queries I've seen are more aggregate data, not tracking on individual users. You might be able to use segments... but Google's quota policy would also put crimp on any kind of data-intensive analysis.
Comment #3
danithaca commentedThanks grendzy. I'm not sure whether the module can use GA Event Tracking with user_id and node_id. This might be dependent on #231451: Add hook to alter data before sending it to browser
Comment #4
generalredneckWow, I was just thinking... wouldn't it be cool if the Recommender API had a plugin that used Google Analytics Reports as a backbone... possibly driving off of events... To my surprise this was talked about 4 years ago. I wish I had something else to add here as I do "Trending" views using Google Analytics Reports...
I know there is a way to send of a unique id for users using google analytics (besides custom dimensions). Is it possible to use something like that to query for people with more than one or 2 page views that we could then check out the events that those users went through...
Just brain dumping...
In any case, this might be a different module all together.