Closed Bug 977461 Opened 12 years ago Closed 11 years ago

Please port Google Analytics data to Google Big Query

Categories

(Websites :: Web Analytics, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bsullins, Assigned: garethc)

Details

Google Analytics (GA) is in wide-spread use at Mozilla and provides great insight into how many of our efforts are performing. The one challenge with GA is that when web properties receive a large number of hits their API stops returning the full result set and instead provides a sample population. This works for much of our analysis but when the subject of our analysis requires us to speak in absolutes it is a show stopper. Fortunately, Google has a solution for this by the name of Big Query. Google Big Query (BQ) is a web scale anlaytics database living on their cloud platform that offers the ability to query Terabytes of data in under 10's of segments. In June 2013 Google announced that GA enterprise clients, like us, may propagate unsampled GA data over to BQ for analysis, allowing us to speak in absolutes for those types of analysis that require it. I am requesting that for the www.mozilla.org (marketing) profile in GA we port all of the data over to BQ for analysis as several of our engagement teams could benefit from this. Please let me know questions you have and I am happy to help with the implementation. Thanks!
Assignee: server-ops-webops → nobody
Component: WebOps: Engagement → Bedrock
Product: Infrastructure & Operations → www.mozilla.org
QA Contact: nmaul
Component: Bedrock → Analytics
OS: Mac OS X → All
Hardware: x86 → All
Component: Analytics → Web Analytics
Product: www.mozilla.org → Websites
Version: other → unspecified
Is this the correct component? Who can I talk to about pushing this forward? Chris would you be able to help?
Flags: needinfo?(chrismore.bugzilla)
(In reply to bsullins from comment #1) > Is this the correct component? Who can I talk to about pushing this forward? > Chris would you be able to help? It would be Gareth and I that you need to talk to. Can you provide docs or say specifically what would need to be changed to integrate into bq?
Flags: needinfo?(chrismore.bugzilla)
Chris, it looks like we need to contact our GA account manager and then they can enable it. Here is a guide from google https://support.google.com/analytics/answer/3437618?hl=en&ref_topic=3416089 Here are my 2 use cases right now. I suspect there are many more. Let me know how else I can help 1 - The Snippets team wants to be able to calculate click-through-rate (CTR) for snippets based on impressions which are derived from weblogs and surfaced up in Vertica however it is almost impossible to get an unsampled set off the www.mozilla.org property 2 - The same is true for the marketplace team. They are looking to correlate things like ADIs to GA stats on marketplace but often run into the sampling issue.
Assignee: nobody → garethcull.bugs
(In reply to bsullins from comment #3) > Chris, it looks like we need to contact our GA account manager and then they > can enable it. Here is a guide from google > https://support.google.com/analytics/answer/3437618?hl=en&ref_topic=3416089 > > Here are my 2 use cases right now. I suspect there are many more. Let me > know how else I can help > > 1 - The Snippets team wants to be able to calculate click-through-rate (CTR) > for snippets based on impressions which are derived from weblogs and > surfaced up in Vertica however it is almost impossible to get an unsampled > set off the www.mozilla.org property > > 2 - The same is true for the marketplace team. They are looking to correlate > things like ADIs to GA stats on marketplace but often run into the sampling > issue. I've reached out to my GA account manager about proceeding. Stay tuned!
Everything is set up to port GA to BigQuery. All that needs to be done is to ensure that analytics-processing-dev@system.gserviceaccount.com is added as a user to the BigQuery project created.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.