Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/okgrow/analytics
UNMAINTAINED! - Complete Google Analytics, Mixpanel, KISSmetrics (and more) integration for Meteor
https://github.com/okgrow/analytics
analytics google-analytics javascript kissmetrics meteor mixpanel segment
Last synced: 29 days ago
JSON representation
UNMAINTAINED! - Complete Google Analytics, Mixpanel, KISSmetrics (and more) integration for Meteor
- Host: GitHub
- URL: https://github.com/okgrow/analytics
- Owner: okgrow
- License: mit
- Created: 2015-01-26T18:17:56.000Z (almost 10 years ago)
- Default Branch: master
- Last Pushed: 2019-01-22T22:01:31.000Z (almost 6 years ago)
- Last Synced: 2024-05-18T17:45:49.316Z (6 months ago)
- Topics: analytics, google-analytics, javascript, kissmetrics, meteor, mixpanel, segment
- Language: JavaScript
- Homepage: https://atmospherejs.com/okgrow/analytics
- Size: 323 KB
- Stars: 213
- Watchers: 15
- Forks: 61
- Open Issues: 18
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: License.md
Awesome Lists containing this project
- awesome - analytics - UNMAINTAINED! - Complete Google Analytics, Mixpanel, KISSmetrics (and more) integration for Meteor (JavaScript)
README
# Analytics
> Complete Google Analytics, Mixpanel, KISSmetrics (and more) integration for Meteor
**NOTE:** This pkg is **no longer being actively maintained**, if you'd like to maintain this pkg please express interest by opening an issue.
OK GROW! analytics uses a combination of the browser [History API](https://developer.mozilla.org/en-US/docs/Web/API/History), Meteor's [accounts](https://guide.meteor.com/accounts.html) package and Segment.io's [analytics.js](https://segment.com/docs/libraries/analytics.js/) to automatically record and send user identity and page view event data from your Meteor app to your analytics platforms.
## Table of Contents
- [Background](#background)
- [Analytics 3.0+](#analytics-30)
- [Analytics 2.1.0+](#analytics-210)
- [Pre Meteor 1.3.1](#pre-meteor-131)
- [Install](#install)
- [Usage](#usage)
- [Currently Supported Analytic Services](#currently-supported-analytic-services)
- [Page views](#page-views)
- [Routers](#routers)
- [React Router](#react-router)
- [Flow Router](#flow-router)
- [Iron Router](#iron-router)
- [Disabling automatic page views](#disabling-automatic-page-views)
- [Log signin/signout](#log-signinsignout)
- [Event tracking](#event-tracking)
- [Track visitor scrolling](#track-visitor-scrolling)
- [Browser Policy](#browser-policy)
- [Example browser policy](#example-browser-policy)
- [Debugging](#debugging)
- [URL Whitelisting on Android Devices](#url-whitelisting-on-android-devices)
- [Ad-blocker](#ad-blocker)
- [Example React, Flow and Iron Router Apps](#example-react-flow-and-iron-router-apps)
- [Maintainers](#maintainers)
- [Contributing](#contributing)
- [License](#license)
## Background
### Analytics 3.0+
In version 3.X of _this_ package, the automatic page view tracking is handled by our new _router-agnostic_ [`@okgrow/auto-analytics`](https://www.npmjs.com/package/@okgrow/auto-analytics) NPM package, which can be used by _any_ JavaScript application whether using Meteor or not. _This_ package adds automatic user identification by using hooks in the Meteor accounts package and building on Segment.io's `analytics` package _through_ the `@okgrow/auto-analytics` package.
### Analytics 2.1.0+
Our Analytics package has been rewritten to be router agnostic. You should be able to use this package with any router that you use with Meteor app. We have tested and used our Analytics package with iron-router, flow-router, and react-router. You can view and test this out in our iron-router, flow-router and react-router example apps located in the `examples` folder.
**NOTE**: A fundamental change that may affect some applications is that we no longer look for or use the router's route name when logging page views. Instead we use `document.title`. This may affect applications that do not change or set their `document.title` for each screen or page of their application. The simplest solution is to simply set document title like this `document.title = "My new title";` for each screen or page in your application. If you are using `flow router` or `iron router` you can remain at `okgrow:[email protected]` to keep using the `name` of the route for your analytic events.
### Pre Meteor 1.3.1
For Meteor Apps older than v1.3.1, please use [v1.0.9](https://github.com/okgrow/analytics/releases/tag/v1.0.9) of this package. Going forward this package will officially only be supporting Meteor Apps >= v1.3.1
## Install
In your [Meteor](https://www.meteor.com) project folder, run:
```sh
meteor add okgrow:analytics
```
## Usage
This package will automatically configure the underlying `@okgrow/auto-analytics` package using `Meteor.settings.public.analyticsSettings`. In Meteor you typically specify your settings using a `settings.json` file:
```js
{
"public": {
"analyticsSettings": {
// Add your analytics tracking ids here (remove this line before running)
"Google Analytics" : {"trackingId": "Your tracking ID"},
"Amplitude" : {"apiKey": "..."},
"Chartbeat" : {"uid": "..."},
"comScore" : {"c2": "..."},
"HubSpot" : {"portalId": "..."},
"Intercom" : {"appId": "..."},
"Keen IO" : {"projectId": "...", "writeKey": "..."},
"KISSmetrics" : {"apiKey": "..."},
"Mixpanel" : {"token": "...", "people": true},
"Quantcast" : {"pCode": "..."},
"Segment.io" : {"apiKey": "..."}
}
}
}
```
And run your app with that settings file as follows:
`meteor --settings settings.json`
See the [`@okgrow/auto-analytics`](https://www.npmjs.com/package/@okgrow/auto-analytics) package for more details on configuration.
### Currently Supported Analytic Services
See the [`@okgrow/auto-analytics`](https://www.npmjs.com/package/@okgrow/auto-analytics) package for up-to-date details of supported analytics services.
### Page views
See the [`@okgrow/auto-analytics`](https://www.npmjs.com/package/@okgrow/auto-analytics) package for details on page view tracking. In short, that package uses the browser [History API](https://developer.mozilla.org/en-US/docs/Web/API/History) to automatically track page views.
Since the History API is used to automatically track page views, `document.title` is used instead of the router's route name as the default page name.
If you rely on your router's route name for the page name in page view events, you can easily set `document.title` programming using the router's route name. Here are examples of how to do this with React Router, Flow Router and Iron Router:
### Routers
This package is router agnostic. It will work with any router, and by default it uses the `document.title` as the page name for reporting to your analytics service.
#### React Router
In your router setup, add a name property to your routes:
```js
```
**NOTE** The current route is passed in as a property named `route` to your component.
Then, in the `render()` function of your main layout component, using a package like [`react-document-title`](https://github.com/gaearon/react-document-title):
```js
render() {
return (
...
);
}
```
#### Flow Router
```js
Template.mainLayout.onRendered(function() {
Tracker.autorun(() => {
document.title = FlowRouter.getRouteName();
});
});
```
#### Iron Router
```js
Template.mainLayout.onRendered(function() {
Tracker.autorun(() => {
document.title = Router.current().route.getName();
});
});
```
### Disabling automatic page views
To disable automatic page view tracking change `Meteor.settings` as shown below then manually log a page view by calling `analytics.page('page name')`:
```js
{
"public": {
"analyticsSettings": {
// Disable autorun if you do not want analytics running on every route (remove this line before running)
"autorun" : false
}
}
}
```
### Log signin/signout
If you have the `accounts` package installed, this package will automatically track when a user logs in and logs out. Logging in will call `identify` on the user and associate their `Meteor.userId` to their previous anonymous activities.
### Event tracking
See the [`@okgrow/auto-analytics`](https://www.npmjs.com/package/@okgrow/auto-analytics) package for details on event tracking. In short, track any event by calling the `analytics.track()` function:
```js
analytics.track("Bought Ticket", {
eventName: "Wine Tasting",
couponValue: 50,
});
```
### Track visitor scrolling
Josh Owens' article, [Google Analytics events, goals, and Meteor.js](http://joshowens.me/google-analytics-events-goals-and-meteor-js/), goes over a great way to capture how far a visitor has scrolled down a page.
### Browser Policy
If your project uses the [Browser Policy package](https://atmospherejs.com/meteor/browser-policy), we've included the Google Analytics and MixPanel domains in our browser policy configuration. Any additional services you add will need to be added to your browser policy config as well.
#### Example browser policy
```html
BrowserPolicy.content.allowOriginForAll("www.google-analytics.com");
BrowserPolicy.content.allowOriginForAll("cdn.mxpnl.com");
```
If your project doesn't use the Browser Policy package, don't worry, it won't affect your usage.
## Debugging
To log package activity to the console for debugging purposes, turn on debugging in the console:
`> analytics.debug()`
Turn debug logging off with:
`> analytics.debug(false)`
### URL Whitelisting on Android Devices
If your app is running on Android devices you will probably have to add the `cordova-plugin-whitelist` package and set access rules in your `mobile-config.js` for all URLs of the platforms that you are using.
Example for Intercom:
```
App.accessRule('https://js.intercomcdn.com/*');
App.accessRule('https://static.intercomcdn.com/*');
App.accessRule('https://api-iam.intercom.io/*');
App.accessRule('https://widget.intercom.io/*');
App.accessRule('https://nexus-websocket-a.intercom.io/*');
App.accessRule('https://nexus-websocket-b.intercom.io/*');
```
To find all the necessary URLs for your project, build your production app and install it on your Android device. Then connect it via USB and open the Android Studio Device Monitor (Tools >> Android Device Monitor >> LogCat). Perform a relevant action and then search for "whitelist". It should a show message for each URL that was blocked.
### Ad-blocker
When running your Meteor app in "development mode" ad-blocking web-browser extensions may block the `okgrow:analytics` package due to the word "analytics" in the package name. This only occurs when running Meteor in "development mode" because files are not bundled together and minified. To work around this issue you can disable your ad-blocker when running in development mode.
To test that application with an ad-blocker, run your Meteor app in production mode with this command:
`meteor run --production --settings settings.json`
**NOTE** If an ad-blocker is enabled the expected behavior is that analytic events will not be received. You'll see an error message in your console reporting the events being blocked.
## Example React, Flow and Iron Router Apps
While page view event tracking is router agnostic, the `examples` directory contains example apps using the three most common routers used in Meteor apps: [React Router](https://github.com/ReactTraining/react-router/tree/master/packages/react-router), [Flow Router](https://github.com/kadirahq/flow-router) and [Iron Router](https://github.com/iron-meteor/iron-router). These apps can be run from within their respective directories with:
```sh
meteor npm start
```
## Maintainers
This is an open source package. We hope to deal with contributions in a timely manner, but that's not always the case. The main maintainers are:
[@okgrow](https://github.com/okgrow)
Feel free to ping if there are open issues or pull requests which are taking a while to be dealt with!
## Additional Notes
There has been at least one report of Google Analytics taking over a day in between GA account creation and any data showing up on the actual GA dashboard. See [this issue](https://github.com/okgrow/analytics/issues/192#issuecomment-333674998) for details. You may just need to wait if nothing's showing up.
## Contributing
Issues and Pull Requests are always welcome.
Please read our [contribution guidelines](https://github.com/okgrow/guides/blob/master/docs/OpenSource-Contributing.md).
If you are interested in becoming a maintainer, get in touch with us by sending an email or opening an issue. You should already have code merged into the project. Active contributors are encouraged to get in touch.
Please note that all interactions in @okgrow's repos should follow our [Code of Conduct](https://github.com/okgrow/guides/blob/master/docs/OpenSource-CodeOfConduct.md).
## License
Released under the [MIT license](https://github.com/okgrow/analytics/blob/master/License.md) © 2015-2017 OK GROW!.