analytics-node

What is analytics-node?

The analytics-node npm package is a client for Segment's server-side analytics. It allows you to send data to Segment from your Node.js applications, enabling you to track user actions, identify users, and manage groups. This data can then be routed to various analytics and marketing tools.

What are analytics-node's main functionalities?

Track

The `track` method allows you to record any actions your users perform. This is useful for tracking events like purchases, sign-ups, or any other user activity.

const Analytics = require('analytics-node');
const analytics = new Analytics('YOUR_WRITE_KEY');

analytics.track({
  userId: 'user123',
  event: 'Item Purchased',
  properties: {
    item: 'Sword of Truth',
    price: 300
  }
});

Identify

The `identify` method is used to associate user data with a specific user ID. This helps in creating a user profile with traits like name, email, and other custom attributes.

const Analytics = require('analytics-node');
const analytics = new Analytics('YOUR_WRITE_KEY');

analytics.identify({
  userId: 'user123',
  traits: {
    name: 'John Doe',
    email: '[e-mail]',
    plan: 'premium'
  }
});

Group

The `group` method allows you to associate a user with a group, such as a company or organization. This is useful for B2B applications where you need to track users within the context of their organization.

const Analytics = require('analytics-node');
const analytics = new Analytics('YOUR_WRITE_KEY');

analytics.group({
  userId: 'user123',
  groupId: 'group123',
  traits: {
    name: 'Company XYZ',
    industry: 'Technology'
  }
});

Page

The `page` method is used to record page views on your website. This is useful for tracking which pages users are visiting and how they navigate through your site.

const Analytics = require('analytics-node');
const analytics = new Analytics('YOUR_WRITE_KEY');

analytics.page({
  userId: 'user123',
  category: 'Docs',
  name: 'Node.js Library',
  properties: {
    url: 'https://example.com/docs/node'
  }
});

Alias

The `alias` method is used to merge two user identities, effectively linking an anonymous user with an identified user. This is useful when a user signs up or logs in, and you want to associate their previous anonymous actions with their new identified profile.

const Analytics = require('analytics-node');
const analytics = new Analytics('YOUR_WRITE_KEY');

analytics.alias({
  previousId: 'temp123',
  userId: 'user123'
});

Other packages similar to analytics-node

mixpanel

Mixpanel is an advanced analytics service that helps improve web and mobile applications by tracking how users interact & engage with them. It offers similar functionalities to analytics-node, such as tracking events, identifying users, and creating user profiles. However, Mixpanel also provides more advanced features like A/B testing and in-depth funnel analysis.

amplitude

Amplitude is a product analytics service that helps teams understand user behavior, ship the right features, and improve business outcomes. Like analytics-node, it allows for event tracking and user identification. Amplitude is known for its powerful analytics capabilities, including cohort analysis, user segmentation, and retention tracking.

heap

Heap automatically captures every user action in your web or mobile app and lets you analyze it all retroactively. It offers similar functionalities to analytics-node, such as tracking events and identifying users. Heap's main advantage is its automatic data capture, which eliminates the need for manual event tracking.

keen.io

Keen.io is a data analytics platform that allows you to collect, analyze, and visualize event data. It provides similar functionalities to analytics-node, including event tracking and user identification. Keen.io is highly customizable and offers powerful data visualization tools, making it a good choice for custom analytics solutions.

README

analytics-node

analytics-node is a node.js client for Segment.io. It's the sister API of the popular analytics.js.

Node Analytics Made Simple

Segment.io is the simplest way to integrate analytics into your application. One API allows you to turn on any other analytics service. No more learning new APIs, repeated code, and wasted development time.

var analytics = require('analytics-node');
analytics.init({apiKey: 'MY_API_KEY'});
analytics.track({userId: '[e-mail]', event: 'Played a Song'});

and turn on integrations with just one click at Segment.io.

... and many more.

High Performance

This client uses an internal queue to efficiently send your events in aggregate, rather than making an HTTP request every time. This means that it is safe to use in your high scale web server controllers, or in your backend services without worrying that it will make too many HTTP requests and slow down the program. You no longer need to use a message queue to have analytics.

Quick-start

If you haven't yet, get an API key here.

Install

npm install analytics-node

Initialize the client

The default and easiest method for most apps is to just use the API client as a module. To get started, just initialize it once:

var analytics = require('analytics-node');
analytics.init({apiKey: 'MY_API_KEY'}});

Then whenever you require('analytics-node') from any other file your app, you'll have access to the same client.

Identify a User

Identifying a user ties all of their actions to an id, and associates user traits to that id.

analytics.identify({
    sessionId : String
    userId    : String
    traits    : Object,
    timestamp : Date
});

sessionId (String) is a unique id associated with an anonymous user before they are logged in. If the user is logged in, you can use null here.

userId (String) is the user's id after they are logged in. It's the same id as which you would recognize a signed-in user in your system. Note: you must provide either a sessionId or a userId.

traits (Object) is a dictionary with keys like subscriptionPlan or age. You only need to record a trait once, no need to send it again.

timestamp (Date, optional) is a Javascript date object representing when the track took place. If the identify just happened, leave it blank and we'll use the server's time. If you are importing data from the past, make sure you provide this argument.

analytics.identify({
    sessionId : 'DKGXt384hFDT82D',
    userId    : '[e-mail]',
    traits    : {
        firstName        : 'Ilya',
        lastName         : 'Volodarsky',
        subscriptionPlan : 'Premium',
        onMailingList    : true
    },
    timestamp : new Date('2012-12-02T00:30:08.276Z')
});

Track an Action

Whenever a user triggers an event, you’ll want to track it.

analytics.track({
    sessionId  : String,
    userId     : String,
    event      : String,
    properties : Object,
    timestamp  : Date
});

sessionId (String) is a unique id associated with an anonymous user before they are logged in. Even if the user is logged in, you can still send us the sessionId or you can just use null.

userId (String) is the user's id after they are logged in. It's the same id as which you would recognize a signed-in user in your system. Note: you must provide either a sessionId or a userId.

event (String) describes what this user just did. It's a human readable description like "Played a Song", "Printed a Report" or "Updated Status".

properties (Object) is a dictionary with items that describe the event in more detail. This argument is optional, but highly recommended—you’ll find these properties extremely useful later.

timestamp (Date, optional) is a Javascript date object representing when the track took place. If the event just happened, leave it blank and we'll use the server's time. If you are importing data from the past, make sure you provide this argument.

analytics.track({
    sessionId : 'DKGXt384hFDT82D',
    userId : '[e-mail]',
    event : 'Listened to a song',
    properties : {
        'Title': 'Eleanor Rigby',
        'Artist': 'Beatles',
        'Playlist': 'Popular'
    },
    timestamp: new Date('2012-12-02T00:30:08.276Z')
});

That's it, just two functions!

Advanced

Batching Behavior

By default, the client will flush:

• the first time it gets a message
• every 20 messages (control with flushAt)
• if 10 seconds has passed since the last flush (control with flushAfter)

Turn off Batching

When debugging, or in short-lived programs, you might want the client to make the request right away. In this case, you can turn off batching by setting the flushAt argument to 1.

analytics.init({ apiKey: 'API_KEY', flushAt: 1 });

Flush Whenever You Want

At the end of your program, you may want to flush to make sure there's nothing left in the queue.

analytics.flush(function (err) {
    console.log('Flushed, and now this program can exit!');
});

Why Batch?

This client is built to support high performance environments. That means it is safe to use analytics-node in a web server that is serving hundreds of requests per second.

How does the batching work?

Every action does not result in an HTTP request, but is instead queued in memory. Messages are flushed in batch in the background, which allows for much faster operation.

What happens if there are just too many messages?

If the client detects that it can't flush faster than it's receiving messages, it'll simply stop accepting messages. This means your program won't crash because of a backed up analytics queue.

Message Acknowledgement

Batching means that your message might not get sent right away.

How do I know when this specific message is flushed?

Every identify and track returns a promise, which you can use to know when that message is flushed.

var analytics = require('analytics-node');

var promise = analytics.track({ userId : '[e-mail]',
                                event  : 'Plays Ultimate' });

promise.on('flush', function () {
    console.log('I'm 2000 miles away now!')
});

promise.on('err', function (err) {
    console.log('Error occured: ', err);
    // [Error: We couldnt find an app with that API_KEY. Have you created it at segment.io? If so, please double check it.]
});

How do I know when any messages are flushed?

You can use the analytics client as an event emitter to listen for any flushes or errors.

var analytics = require('analytics-node');

analytics.on('flush', function () {
    console.log('I just got flushed. YAY!');
});

Error Handling

In order to handle errors, the node client will emit every time an error occurs. To prevent analytics-node from crashing your server with an unhandled exception, it emits on err rather than the more conventional error.

During integration, we recommend listening on the err event to make sure that all the data is being properly recorded.

analytics.on('err', function (err) {
    console.warn('Error occured', err);
    // [Error: We couldnt find an app with that API_KEY. Have you created it at segment.io? If so, please double check it.]
});

Other Events

You may also listen on the following events for more granular information.

• initialize - when the client is initialized and able to record events.
• flush - after the client flushes part of its queue.
• err - when an error in the tracking code or connection happens.

Understanding the Client Options

If you hate defaults, than you'll love how configurable the analytics-node is. Check out these gizmos:

var analytics = require('analytics-node');
analytics.init({
    apiKey        : 'API_KEY',

    flushAt       : 20,
    flushAfter    : 10000,

    maxQueueSize  : 10000,
    timerInterval : 10000,
    triggers      : [analytics.triggers.size, analytics.triggers.time]
});

flushAt (Number) - Flush after this many messages are in the queue. flushAfter (Number) - Flush after this many milliseconds have passed since the last flush. maxQueueSize (Number) - Stop accepting messages into the queue after this many messages are backlogged in the queue. timerInterval (Number) - Check this many milliseconds to see if there's anything to flush. triggers (Array[Function]) - An array of trigger functions that determine when it's time to flush.

Multiple Clients

Different parts of your app may require different types of batching. In that case, you can initialize different analytic-node client instances. The API is exactly the same.

var analytics = new require('analytics-node').Client();
analytics.init({apiKey: 'MY_API_KEY', ...});

Testing

npm test

License

WWWWWW||WWWWWW
 W W W||W W W
      ||
    ( OO )__________
     /  |           \
    /o o|    MIT     \
    \___/||_||__||_|| *
         || ||  || ||
        _||_|| _||_||
       (__|__|(__|__|

(The MIT License)

Copyright (c) 2012 Segment.io Inc. [e-mail]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.