851215 - [Theme] Marketplace Metrics

Status: NEW

(Tracking :: User Story, defect)

Description

[David Bialer [:dbialer]]

Tracking Theme for adding metrics for developers, mozilla, community.
PRD is here:  https://docs.google.com/a/mozilla.com/document/d/1GdeEtfB2PxsuNfg6dT-6Q5leD76Gpkx4ktQQAi5Ta6Y/edit

Comment 1

[Caitlin Galimidi [:c8o]]

David - 
Which system will deliver the metrics below? Want to make sure I pursue the right teams between Marketplace and Google Analytics... 

Per operator and per device 
- # visits 
- # visitors 
- # downloads 
	o free 
	o paid 
- revenues 
- top apps
	o free 
	o paid

Comment 2

[David Bialer [:dbialer]]

This is Marketplace Metrics.

Comment 3

[Wil Clouser [:clouserw]]

> Per operator and per device 
> - # visits 
> - # visitors 
> - # downloads 
> 	o free 
> 	o paid 
> - revenues 
> - top apps
> 	o free 
> 	o paid

I'm fairly sure you can get everything in that list out of GA, aside from revenues.  Gareth could tell you for sure though.  V1 of GA lands tomorrow @ 2pm and then numbers will start rolling in so we can start double checking stuff.  Gareth - do you have time to have a look tomorrow afternoon or Friday?

Comment 4

[Gareth Cull [:garethc]]

Sure. I'm out of the office tomorrow, but I can start to take a look at it this afternoon. Is the consumer implementation being pushed to production at 2pm? 

As for metrics tracked in GA, we should be able to get everything but revenue. Revenue should ideally be pulled from the Metrics team, and not from GA.

Comment 5

[Gareth Cull [:garethc]]

Hey Guys,

I've been working through the implementation and have found some bugs. Still working through the data, and there are some additional things that I would like implemented on the consumer side which were not included in the original specs (ie. Popular vs. New Tab interaction, etc). I'm going to add these to the tagging requirements doc for later.

Summary of bugs found:

1. Page Level Custom Variables (6-10) are being set on subsequent pages after initially being set on App View Page. Can we please set these only on the app description page? 

I'm going to send you additional Google Debugger data so you can see the Custom Vars being set on subsequent pages after the initial set. This will show you an example as i navigated from home to the AirBnB app and then back to home.

2. Custom Var 3 should be set on initial load of marketplace, but is not being registered. It looks like this might be set after the initial _trackPageview. Custom vars need to be set prior to trackPageview or an event.

3. 2 image requests (trackPageViews) are being sent back to GA in some cases (refresh, when a user logs in, and in potentially other areas). This is occurring site wide on the consumer side only. I'm seeing one trackPageview being called containing no url parameters (standard way to call trackPageview), the other contains a parameter with the value of the location url: 
_gaq.push(["_trackPageview",e.location.href]). 

Matt, I believe mentioned you were looking into this fix #3 (we initially saw it on the home page, but it seems to site wide). Can you please remind me why we included e.location.href? Is this because of fireplace? We only need to call trackPageview once per page. 

Thanks for your help on this!

Gareth

Comment 6

[Chris More [:cmore]]

:basta ^^

Comment 7

[Chris More [:cmore]]

https://developers.google.com/analytics/devguides/collection/gajs/methods/gaJSApiBasicConfiguration#_gat.GA_Tracker_._deleteCustomVar

Comment 8

[David Bialer [:dbialer]]

All of these are accessible in Google Analytics, except revenue.  Also not segmented by carrier and network.  However, I do want to make a distinction between analytics and metrics - at least for external usage.  The metrics reports in the PRD is for integration and dashboards, and for use by external parties.

If Comment 1 refers to getting these reports to operator partners, we could automoatically generate reports and have them emailed to operators from GA as a PDF, CSV, or Excel spreadsheet on a periodic basis. I think we want to keep these areas separate though the information for metrics reports can be pulled from GA.

Comment 9

[Matt Basta [:basta]]

This should fix issue #1 above:

https://github.com/mozilla/fireplace/commit/a76d3f731db449b14ff087382bf4821cf7a4f126

Comment 10

[Gareth Cull [:garethc]]

Hey Matt,

I just noticed another thing that would be great to have. The number of times people click on the Launch button after a user installs an app from marketplace.

So the event flow we would be tracking would be: 
Click to Install > Success > Launch App

Can you please add the following GA event? The implementation is similar to the install event you added from the tracking requirements doc (row 6 - without the value)

_gaq.push(['_trackEvent','Launch App','Free' OR 'Paid','[Name of App]:[AppId]');

Thanks!

Comment 11

[Matt Basta [:basta]]

https://github.com/mozilla/fireplace/commit/0c260ebc0ddc1dbe751f972caf6bffa3f373e501

This should track launch events, but it will report the app's slug rather than name/id (for the same reasons noted in the other GA bug).