Angularytics vs. Angulartics

Dave Ceddia bio photo By Dave Ceddia Comment

There’s been a bit of confusion about these two libraries, what they do, and how they differ.

Seeing as the sites don’t mention anything about each other, I thought it would be useful to at least declare that they are in fact different.

If you ended up here, the main thing you need to know is:

Angularytics is not the same as Angulartics

One of them has a ‘y’ in it, and that letter makes all the difference.

Here’s what they do:

Angularytics

From their Github page, the main features are:

  • It automatically tracks new page views with all connected providers (Google Analytics and console.log) when the URL in your app changes.
  • Lets you track events, either using the Angularytics service or by using the trackEvent filter

The library appears to be pretty no-frills and only supports Google Analytics as of this writing.

Angulartics

This library, on the other hand, supports a range of analytics platforms out of the box - Google Analytics, Kissmetrics, Mixpanel, Flurry, Piwik, Segment.io, “and more.” It’s got nearly twice the number of stars on Github, 7x the contributors, and easy-to-use directives for tracking events.

It also automatically tracks page views (which they call “virtual pageview tracking”).

You can learn more at their Github page

“Which one should I use?”

Angulartics (without the ‘y’) looks like the more well-supported and feature-complete of the two. It also has stronger community support, and seems to be the de-facto standard analytics library for AngularJS. If you’re not sure, go with Angulartics.

Choosing a framework is difficult.

Learning React? Sign up and get my React Learning Timeline PDF, and also weekly-ish articles about React, Angular, and JavaScript.

A few emails per month — unsubscribe any time.
comments powered by Disqus