[Analytics] Why Google Analytics? Keen IO would be better – enable stats for packages #152

Closed
nemo opened this Issue Apr 26, 2016 · 16 comments

Projects

None yet

4 participants

@nemo
nemo commented Apr 26, 2016 edited

One thing I love about npm is the fact that there are stats about every package on their system.

They can afford doing stuff like that since they're a corporation. But I think Homebrew could do the same by using something like Keen IO to track everything and either give out the read key to the community (so people can judge the packages in terms of their download popularity etc.) or create a simple service to show stats on packages to maintainers or the community at large.

I believe they offer a free for OSS deal – so it won't cost anybody anything (other than the time cost to switch from Google to Keen IO) and I for one would love to see it happen.

$5 says if we email them, we can actually get them to help with the integration 💯

@nemo nemo changed the title from [Analytics] Why Google Analytics? KeenIO would be better – enable stats for packages to [Analytics] Why Google Analytics? Keen IO would be better – enable stats for packages Apr 26, 2016
@bfontaine
Member

That sounds interesting. Note we already have public stats on bottles (i.e. precompiled packages) via Bintray, e.g.: https://bintray.com/homebrew/bottles/git/view#statistics

@nemo
nemo commented Apr 26, 2016

@bfontaine cool! Hadn't seen that. Kind of what I was looking for (though I have to go through 3 clicks to get the data)

Anyway – implementing Keen IO shouldn't take any more time than Google Analytics did. I'm surprised GA can support non-web tracking – I expect half the dashboards to be completely useless on it.

I just think it'd be cool to expose the data eventually to the community so others can learn from it and understand homebrew's scale :)

@MikeMcQuaid
Member

@nemo Thanks for the issue. A few questions:

  • How long has Keen IO been around and what's their revenue model like? I want to avoid moving somewhere that doesn't exist in a year.
  • Have you personally used it? Do you like it? Can you make an introduction?
  • Can you link to e.g. the OSS plan?

Thanks for this; definitely open to other options here.

@nemo
nemo commented Apr 26, 2016 edited

@mikemcquaid Anytime! Here's a few responses:

  • Keen IO has been around for a few years and as far as I know – they're going pretty strong.
  • I've been a user through 3 separate companies in the past 4 years and we're currently a user at Suto and very happy with it :)
  • I can definitely make an introduction to someone there – they have a few community folks who could probably help out here. cc: @elof
  • Look for "Open Sourcer?" on this page for the OSS plan.
@elof
elof commented Apr 26, 2016

Hey all. I'm a community person from Keen and would be happy to help out. We support OSS projects with free upgraded accounts (but not unlimited).

To answer some of @mikemcquaid's questions.

  • The company was founded in Jan of 2012 (went through Techstars) and we are backed by Sequoia.
  • Our business model for small volume accounts (<15million events/month) is to charge for volume, for large volume accounts there can be many factors that go into what we charge.

Here are some examples of OSS teams that we work with: https://github.com/keen/community-team/blob/master/community-projects.md

@MikeMcQuaid
Member

Thanks @nemo and @elof. That sounds interesting and I'll check it out more.

@MikeMcQuaid
Member

Anyone else who comments on this thread to complain about our analytics rather than to discuss Keen.io specifically will have their comment deleted and be blocked from the Homebrew organisation temporarily. I want to talk to @nemo and @elof here so cannot lock this thread.

@MikeMcQuaid
Member

@elof Not sure about monthly events yet but got 1,151,671 total events last week. Would this be too many for Keen to handle for free?

@elof
elof commented May 3, 2016

@mikemcquaid that data amount shouldn't be a problem, but I'd like to connect with you to discuss how you plan to surface the data (i.e. what queries you will be running and where the metrics will be embedded)

@MikeMcQuaid
Member

@elof Ok, feel free to email me at mike@mikemcquaid.com or just chat here. Where's not sure yet what queries we'll be running but most likely just aggregates e.g. how many people did X vs Y.

@elof
elof commented May 5, 2016

Ok, that sounds fine. Do you plan on embedding any of the metrics places
where the public would view?

On Wed, May 4, 2016 at 1:16 AM Mike McQuaid notifications@github.com
wrote:

@elof https://github.com/elof Ok, feel free to email me at
mike@mikemcquaid.com or just chat here. Where's not sure yet what queries
we'll be running but most likely just aggregates e.g. how many people did X
vs Y.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#152 (comment)

@MikeMcQuaid
Member

We do not but we were thinking of providing people with either sporadic data dumps or the read-only key to the data.

@elof
elof commented May 10, 2016

@mikemcquaid 👍 hit me up when you start sending data so I can update your account.

@MikeMcQuaid
Member

@elof Is there anything else I need to know or do? Just want to make extra sure we're not going to hit any limits in the medium-long term and we'll be able to run queries on that data OK in a performant fashion. Thanks!

@elof
elof commented May 11, 2016

@mikemcquaid all set. When you start running queries that you know you are going to run on a regular basis create a saved query and make sure it's cached. They will be 🏇

@MikeMcQuaid
Member

Thanks for all the input folks. I've played around with the implementation here but we've decided to not move to Keen at this time for a few reasons that I'm happy to detail privately. I am going to look into providing sporadic community data dumps of Google Analytics so our community can check out the data. Thanks!

@MikeMcQuaid MikeMcQuaid locked and limited conversation to collaborators Jun 11, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.