Bugzilla – Bug 14109
add Google Analytics event tracking
Last modified: 2010-05-03 16:28:22 UTC
In order to measure usage trends in the new UI, we need to add some Google Analytics event tracking. The following is a guideline based on things I know we will want to see, but feel free to use your judgment and add any addition tracking you think would be interesting/useful to see. Format is: _trackEvent(category, action, optional_label, optional_value) from ( http://code.google.com/apis/analytics/docs/tracking/eventTrackerGuide.html ) For select language dropdown in global nav: _trackEvent( 'account', 'select language', 'location', 'global layout' ); For saving changes to your account: _trackEvent( 'account', 'save changes', ); For app gallery filter dropdown: _trackEvent( 'app gallery', 'filter apps', 'category name', '[ filter category name ]' ); e.g.: _trackEvent( 'app gallery', 'filter apps', 'category name', 'Featured Apps' ); For selecting app gallery apps: _trackEvent( 'app gallery', 'select app', 'app name', '[ app name ]' ); e.g.: _trackEvent( 'app gallery', 'select app', 'app name', 'Facebook' ); For scrolling through app list: _trackEvent( 'app gallery', 'scroll app list', 'direction', 'up' ); For scrolling through homepage slideshow: _trackEvent( 'homepage', 'scroll slideshow', 'direction', 'next' ); (or 'previous') For scrolling through homepage app list: _trackEvent( 'homepage', 'scroll app list', 'direction', 'next' ); (or 'previous') For app gallery "Please log in to install this app.": _trackEvent( 'app gallery', 'click log in to install', 'app name', '[the app name]' ); e.g.: _trackEvent( 'app gallery', 'click log in to install', 'app name', 'BBC' ); For my apps uninstall an app -- _trackEvent( 'my apps', 'uninstall', 'app name', '[app name]' ); For player settings -- on selecting a product: _trackEvent( 'players', 'select player', 'device type', '[device type]' ); _trackEvent( 'players', 'select player', 'device type', 'Squeezebox Boom' ); Note for device type -- this can use whatever is already built into MySb as far as player type identifiers as long as it is human readible on saving changes: _trackEvent( 'players', 'save changes', 'device type', '[device type]' ); For player settings tabs -- _trackEvent( 'players', 'select tab', 'tab name', '[tab name]' ); e.g.: _trackEvent( 'players', 'select tab', 'tab name', 'Alarms' );
> For saving changes to your account: This might be a problem, as this isn't one very specific button, but an item which is dynamically added by a script whenever there's a placeholder somewhere on the page. But there can easily be several of them. We could probably make it something like _trackEvent( '[ page we're on]', 'submit pressed', 'action', '[ some attempt of defining what the button did, eg. install something ]' ); > For scrolling through app list: Just tracking the event that the button has been pressed? Again - this is dynamically built code, it might get used in other places too. I'll see what we can do. > For app gallery "Please log in to install this app.": See above: all those nice buttons are dynamically built. I'll try to come up with a list of what we have, and an attempt to categorize them. > _trackEvent( > 'players', > 'select player', > 'device type', > '[device type]' > ); Heck... why would this be interesting?!? After all this will correspond to our sales numbers. Most users have one player only anyway. Incredible what useless amount of data you marketing guys like to have :-P.
Michael, this is about gauging how people interact with MySB.com. It has nothing to do with sales data :-P Usage data is not useless ... from a business perspective, a web application with no usage data is useless unless you can measure the utility of it in some fashion. I could think of plenty snarky comments to retort your statement but I will bite my tongue :-P Your proposal sounds fine -- if it's easier to implement, that's better. Basically just want to see what people are clicking on all over -- normally this is handled by href attribute in google analytics, but since it's all JS driven, we need some JS to track usage information. However you can provide contextual information about actions, that's fine.
Better get this in before launching so that it can be tested. In my experience Google Analytics can really slow a web site down. Surely a company the size of Logitech can afford a good in-house tracking solution.
Google Analytics tracking is already present in the site. Adding a few one line event tracking snippets shouldn't influence performance. On Fri, Sep 18, 2009 at 5:22 PM, <bugs@bugs.slimdevices.com> wrote: > https://bugs-archive.lyrion.org/show_bug.cgi?id=14109 > > > Jim Zolx <jj@zolx.com> changed: > > � � � � � What � �|Removed � � � � � � � � � � |Added > ---------------------------------------------------------------------------- > � � � � � � � � CC| � � � � � � � � � � � � � �|jj@zolx.com > > > --- Comment #3 from Jim Zolx <jj@zolx.com> 2009-09-18 18:22:37 MDT --- > Better get this in before launching so that it can be tested. �In my experience > Google Analytics can really slow a web site down. �Surely a company the size of > Logitech can afford a good in-house tracking solution. > > -- > Configure bugmail: https://bugs-archive.lyrion.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. > You reported the bug. >
Let's have new marketing come up with a new plan.