An official Segment.io client driver for node
This is the official node.js client that wraps the Segment.io REST API .
You can use this driver to identify your users and track their events into your Segment.io project.
This client uses batching to efficiently record your events in aggregate, rather than making an HTTP request every time. This means that it is safe to use in your web server controllers, or in back-end services without worrying that it will make too many HTTP requests and slow down the system.
You can control the batching behavior as described below.
npm install segmentio
The default and easiest method for most apps is to just use the API client as a module. To get started, just use the following:
var segmentio = require'segmentio';segmentioinitisProduction ? 'LIVE_API_KEY' : 'TEST_API_KEY';
Then whenever you
require('segmentio') from your app, you'll have access to the same client.
You can also create your own client if you'd like a little more customization. The API is exactly the same.
var segmentio = 'segmentio'Client;segmentioinitisProduction ? 'LIVE_API_KEY' : 'TEST_API_KEY';
Identifying a user ties all of their actions to an ID you recognize and records user traits you can segment by.
segmentioidentifysessionId : StringuserId : Stringtraits : Objecttimestamp : 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 usually an email, but any unique ID will work. This is how you recognize a signed-in user in your system. Note: it can be null if the user is not logged in. By explicitly identifying a user, you tie all of their actions to their identity. This makes it possible for you to run things like segment-based email campaigns.
traits (object) is a dictionary with keys like “Subscription Plan” or “Favorite Genre”. You can segment your users by any trait you record. Once you record a trait, no need to send it again, so the traits argument is optional.
timestamp (Date) is a Date object representing when the identify took place. It is optional, and if not provided, server-now will be used.
segmentioidentifysessionId : 'DKGXt384hFDT82D'userId : 'email@example.com'traits :'First Name': 'Ilya''Last Name': 'Volodarsky''Subscription Plan': 'Premium''On Mailing List': truetimestamp: '2012-12-02T00:30:08.276Z';
Whenever a user triggers an event on your site, you’ll want to track it so that you can analyze and segment by those events later.
segmentiotracksessionId : StringuserId : Stringevent : Stringproperties : Objecttimestamp : 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. Either this or the userId must be supplied.
userId (string) is usually an email, but any unique ID will work. This is how you recognize a signed-in user in your system. Note: it can be null if the user is not logged in. By explicitly identifying a user, you tie all of their actions to their identity. This makes it possible for you to run things like segment-based email campaigns. Either this or the sessionId must be supplied.
event (string) is a human readable description like "Played a Song", "Printed a Report" or "Updated Status". You’ll be able to segment by when and how many times each event was triggered.
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) is a Date object representing when the track took place. It is optional, and if not provided, server-now will be used.
segmentiotracksessionId : 'DKGXt384hFDT82D'userId : 'firstname.lastname@example.org'event : 'Listened to a song'properties :'Title': 'Eleanor Rigby''Artist': 'Beatles''Playlist': 'Popular'timestamp: '2012-12-02T00:30:08.276Z';
You can adjust the flush triggers in the client. Take a look into the source.
In order to handle errors, the node client will emit every time an error occurs. To prevent the segmentio client from crashing your server with an unhandled exception, it emits on
err rather than the more conventional
During integration, we recommend listening on the
err event to make sure that all the data is being properly recorded:
segmentioon'err' console.warn'A segment.io error occured' err; ;
You may also listen on the following events for more fine-grained granularity.
- flushed - when the client has sent its queue to the server
- flushing - when the client is in the process of submitting its queue
- err - when an error in the tracking code or connection happens.
- initialized - when the client is initialized and able to record events.
(The MIT License)
Copyright (c) 2012 Segment.io Inc. email@example.com
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.