Automatic user events collection for Meteor


If you’ve ever instrumented your app for tools like Mixpanel, KISSmetrics, Intercom, Hubspot, RJMetrics, or Keen IO, you know the pain.

It can take weeks to collaborate what to track, and get the code added, tested, and deployed. And with each new feature, the decision on “should we track this too” is raised. Switching tools is extremely painful too.

Not fun. It feels like you’re always a few steps back on the problem.

What if it could take 5-minutes?

Starting with the Meteor framework, we aim to remove this pain for devs and product owners. For Meteor devs, it’s a five-minute process now:

@astronomerio + in 4:47! Read the docs, signed up (inc GA), deployed to modulus & tested @nwientge @hellogerard

— Conrad VanLandingham (@conrad_vanl) July 1, 2015


The beautiful thing is that any new features you add are automatically instrumented too, automatically.

If Google can make self-driving cars, we can make apps that self-report user events :slight_smile:

Decoupling the work

With our platform, the devs setup Astronomer right before “going live” — the product team select tools whenever (historical data is imported with a click, when new tools are setup).

Why did we start with Meteor?

It’s 10x easier for us to build Astronomer for Meteor apps than it’ll be for other frameworks and framework combinations, because of how Meteor is architected.

While there can be some negatives of a simple, small framework — the net benefits are immense. We’re big fans.

Why track everything?

  • It takes more time to think about what to track, than to just track everything.
  • You can’t analyze data that you don’t have. The cloud tools are in place now to make it cheap to store and analyze terabytes of data.
  • Machine learning tools (which are becoming more and more accessible) function best with as much data as you can provide.

Our alpha program for Meteor devs is live. Consider yourself invited :)