A very very simple abstraction layer for analytics code. Write your events once, then send them where ever you want.

Demo

Stats

Number of integrations: 32

Number of tested integrations fully tested / considered stable & production-ready: 14

Would you like to request an integration? We'd love to help out! Open an issue to get started.

If the docs are publicly available or it's supported by Analytics.js, it should be even easier. Link any docs you may have for Analytics.js or the Javascript API, where available.

Installation via NPM

npm install event-layer

Once installed, you'll need to include event-layer.js in your project, and then (optionally) instantiate a new object (aliasing it to a new global, if you prefer). Continue reading to see how that might work.

Installation via CDN

Include the following scripts in your project:

https://cdn.jsdelivr.net/npm/event-layer@latest/event-layer.js

Then follow the instructions below.

What is it?

“Event Layer” is an extensible abstraction layer for working with common third-party Analytics libraries.

Since more or less all analytics libraries work the same way (allowing you to identify and describe users, and track the events which they perform), “Event Layer” creates an abstraction layer and a set of adapters that allow you to write generic Analytics Tracking code once, and update your configuration later to send your data anywhere you need.

How does it work?

1. Install your third-party analytics libraries in your application or website (you don't need to do anything special)
2. Install event-layer.js in your website or app.
3. Instantiate a new instance of EventLayer: (e.g. var Analytics = new EventLayer();).
4. Instead of filling your app or website with service-specific tracking code, write generic code using the “Event Layer” Javascript API (described below).
5. “Event Layer” will detect the third-party Analytics services you have installed on your website or app, and use it's own, community-maintained adapters to propagate your events, in an identical format, to each third-party service, using the latest version(s) of their APIs.
6. (Optional): You can extend “Event Layer” by writing your own custom adapters for third-party services not yet supported. Each adapter only requires about 12 lines of Javascript, and the community is available to help you ship your first PR to “Event Layer”.

Integrations / Services Currently Supported

Integration | Stable ------------ | ------------- Segment.com | ✔️ Mixpanel | ✔️ Google Analytics | ✔️ PostHog | ✔️ Beam Analytics (New!) | ✔️ June.so (New!) | ✔️ Crisp.chat | ✔️ Intercom | ✔️ Sentry | ✔️ Facebook Tracking Pixel | ✔️ Google Tag Manager | ✔️ Heap | ✔️ Amplitude | ✔️ Keen.io | ✔️ Rollbar | ✔️ Talkus | ✔️ Crazy Egg | ✔️ Elev.io | ✔️ Drift | ✔️ Drip | ✔️ Hello Bar | ✔️ Improvely | ✔️ Helpscout | Fullstory | Olark | Calq | Castle | Lucky Orange | BugHerd | Bugsnag | Chameleon | Inspectlet | Qualaroo | Customer.io | Logspot.io |

*We rely on users to report their usage. Feel free to open an issue just to say "I tested ____, and it works!"

Creating a new instance of EventLayer

We realize that not everyone wants to litter their code with calls to a global named “Event Layer”. So you'll probably want to start off by instantiating a new instance of “Event Layer”.

var Analytics = new EventLayer();

You can name it whatever you like, but the examples given below will need to be modified appropriately.

EventLayer.identify(userId, userProperties)

This method allows you to identify the current visitor, and (optionally) describe the user.

Only identify the user, do not describe any user properties:

Analytics.identify('<unique-user-id>');

Identify the user and describe user properties:

Analytics.identify('<unique-user-id>', {
    name: 'John Doe',
    subscribedToNewsletter: false
});

This is similar to the Identify method found in Mixpanel, Heap, and Analytics.js.

EventLayer.track(eventName, eventProperties)

This method allows you to identify the current visitor, and (optionally) describe the user.

Track a simple event, with no event properties:

Analytics.track('click_signup_button');

Track a more complex event, with event properties:

Analytics.track('purchase', {
    amount: 32.00,
    itemCount: 4,
    shippingSpeed: 'next-day'
});

This is similar to the Track method found in Mixpanel, Heap, and Analytics.js.

EventLayer.page(category, name, properties)

This method has been implemented identically to Analytics.js. See documentation for more details. Feel free to open an issue if you have any questions!

EventLayer.alias(userId, previousId)

This method has been implemented identically to Analytics.js. See documentation for more details. Feel free to open an issue if you have any questions!

EventLayer.group(groupId, traits)

This method has been implemented identically to Analytics.js. See documentation for more details. Feel free to open an issue if you have any questions!

EventLayer.fbTrack(eventName, eventProperties)

Send track events to the facebook tracking pixel

This method implements a copy of the track() method above, but it supports events specific to the Facebook Tracking Pixel as well.

See documentation https://developers.facebook.com/docs/facebook-pixel/api-reference for more details on implementing the Facebook tracking pixel on your website.

Writing an Adapter

Below is an example of a blank adapter.

'blank-adapter-template': { // Do not modify this template
    enabled: false, // Change to true once you're completed testing
    test: function () {},
    identify: function (userId, userProperties) {},
    track: function (eventName, eventProperties) {}
}

It has three main components:

1. Test:

This function, once evaluated, should provide an answer to the question “has a specific third-party analytics library been installed on this page? Is it active? Should we try to send events to this service?”

This can be as simple as sniffing the window object for a global variables, and a commonly-used (and not likely to disappear) method or property:

test: function () {
    return window.ga && window.ga.loaded;
}

(A simple example taken from the Google Analytics adapter)

2. identify:

This function takes data from our generic identify method, and passes it along to a third-party library, via an adapter.

This should contain a minimal number of integrity checks and transforms, as well as a lightweight wrapper for the library's identify and/or describe functionality.

identify: function (userId, userProperties) {
    // Send the identify call to Mixpanel's JS library
    if (window.mixpanel && userId) 
        mixpanel.identify(userId);

    // Set people properties on our identified user
    if (window.mixpanel && userProperties) 
        mixpanel.people.set(userProperties);
}

(A simple example taken from the Mixpanel adapter)

3. track:

This function takes data from our generic track method, and passes it along to a third-party library, via an adapter.

This should contain a minimal number of integrity checks and transforms, as well as a lightweight wrapper for the library's event tracking functionality.

track: function (eventName, eventProperties) {
    // Send the tracked event to Heap's JS library
    if (window.heap && eventName) 
    heap.track(eventName, eventProperties);
}

(A simple example taken from the Heap Analytics adapter)

Adding or modifying an adapter on the fly

You can add or modify an adapter on the fly, after you instantiate EventLayer, by calling the addAdapter method.

Analytics.addAdapter('my-analytics', {
    enabled: true,
    test: function () { return true },
    track: function (eventName, eventProperties) { console.log('tracking') }
});

Debugging

You can set window.__debug to true to enable debugging (console output) for EventLayer.

window.__debug = true;

Pull Requests

Yes, Please & Thank you!

To keep things organized, please open an issue for discussion before putting too much work into a pull request. I would feel really bad if you put a lot of work into something, only for it to not make sense to include it or merge the Pull Request.

Also, to help keep things organized, try to submit individual pull requests for each issue, and keep the scope of each issue relatively small.

For example, if you wanted to add a couple of new adapters, split them into multiple pull requests so we can review them individually.

Issues

Something feel broken? Open an issue! Something you feel is missing? Open an issue (Although we may not be able to get to everything, pull requests are most welcome!)

Thanks!