particle-iot/ember-cli-segment

Name: ember-cli-segment

Owner: Particle

Description: Ember CLI addons that provides a clean and easy way to integrate your Ember application with Segment.com

Forked from: josemarluedke/ember-cli-segment

Created: 2016-03-03 01:31:37.0

Updated: 2016-03-03 01:31:38.0

Pushed: 2018-01-03 18:25:53.0

Homepage:

Size: 45

Language: JavaScript

GitHub Committers

UserMost Recent Commit# Commits

Other Committers

UserEmailMost Recent Commit# Commits

README

Ember CLI segment

Build Status Code Climate

Ember CLI addons that provides a clean and easy way to integrate your Ember application with Segment.com.

Installation
Configuration/Logging

Add your Segment WRITE_KEY to the segment config object for Analytics.js to be loaded and configured automatically.

There is an option available to configure the events log tracking, the default value is false. This option is optional, but recommended.

In your config/environment.js

'segment'] = {
ITE_KEY: 'your_segment_write_key',
G_EVENT_TRACKING: true

Version 0.1.x is compatible with ember > 1.13.x

Usage

The addon will add following elements to your CLI project:

Tracking Page Views

Your router will automatically send a page view event to Segment using the method page under window.analytics everytime the URL changes.

If you need to call it manually for some reason, you can do it using the following method on controllers and routes.

.segment.trackPageView();

The method trackPageView can receive a parameter that's the page url, if not provided it will fetch from window.location.

Additionally you can use the mixin in order to use this method where outside controllers and routes.

Importing the mixin is really simple:

rt segmentMixin from 'ember-cli-segment/mixin';

The mixin can be applied to any Ember object.

Tracking Other Events

You will probabily need to track other events manually as well. We got you covered! Since we have an object called segment in your controllers and routes, it's really straightforward to do it.

Let's say that you need to track an event when the user submits an form in your router.

ile: app/routes/posts/new.js
rt Ember from 'ember'

rt default Ember.Route.extend({
tions: {
submit: function() {
  this.segment.trackEvent('Creates a new post');
}


trackEvent can receive additional properties as well:

.segment.trackEvent('Creates a new post', { title: "Creating a Ember CLI application" });

All the parameters you can provide are: event, properties, options, callback in this order.

Identifying the User

We will automatically call identifyUser method from your application route everytime the URL changes. Inside this method, you should call segment.identifyUser passing the parameters that you want to send to Segment.

ile: app/routes/application.js
rt Ember from 'ember';

rt default Ember.Route.extend({
entifyUser: function() {
this.segment.identifyUser(1, { name: 'Josemar Luedke' });


You should have in mind that you should make a conditional validation to check if the user is currently logged in. For example:

rt Ember from 'ember';

rt default Ember.Route.extend({
entifyUser: function() {
if (this.get('currentUser')) {
  this.segment.identifyUser(this.get('currentUser.id'), this.get('currentUser')));
}


All the parameters you can provide are: userId, traits, options, callback in this order.

aliasUser

Additionally we have an aliasUser method avaliable on segment.aliasUser that you can use when the user logs in in your application.

All the parameters you can provide are: userId, previousId, options, callback in this order.

Running Tests
Contributing
  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

License

Copyright (c) 2015 Josemar Luedke

Licensed under the MIT license.


This work is supported by the National Institutes of Health's National Center for Advancing Translational Sciences, Grant Number U24TR002306. This work is solely the responsibility of the creators and does not necessarily represent the official views of the National Institutes of Health.