How does analytics library abstraction work? 1. User activity triggers analytics.track() 2. Events run through plugins 3. Data is validated, redacted, enriched, or even cancelled 4. Data is then sent to your own backend or any third party provider ✨ npmjs.com/package/analytics

Analytics is an open source analytics abstraction library for browsers & @nodejs It's pluggable & designed to work with third party tools like @googleanalytics, @CustomerIO, @CrazyEgg, @SimpleAnalytic, @fullstory, @HubSpot etc including your own backend! npmjs.com/package/analytics

📈 Analytics is designed to work with any third party analytics tool via plugins. Plugins are just plain javascript objects that expose methods for analytics to register and call. This is the signature of a typical analytics provider plugin: getanalytics.io/plugins/writ…

The analytics library comes with a large variety of event listeners 👂 `analytics.on` & `analytics.once` can be used to fire custom functionality when a specific lifecycle event occurs. 📕 Examples in the docs: getanalytics.io/using-listen…

A huge focus of the `analytics` package is an improved developer experience 😎 Adding `debug: true` will enable time travel debugging for all analytic events flowing through your app. This makes troubleshooting & app telemetry easy 🚀 getanalytics.io/debugging/

Identifying a new user with `analytics` All tracking is fully customization via plugins 🎉 For example, you can allow visitors to opt out of analytics completely and all tracking will noOp. See the "Do Not Track" plugin for an example of this: getanalytics.io/plugins/do-n…

Autocomplete for React Component PropTypes bit.ly/29ySjgY