react-ga

React Google Analytics Module

This is a JavaScript module that can be used to include Google Analytics tracking code in a website or app that uses React for its front-end codebase. It does not currently use any React code internally, but has been written for use with a number of Mozilla Foundation websites that are using React, as a way to standardize our GA Instrumentation across projects.

It is designed to work with the latest version of Google Analytics, Universal Analytics. At this point, all Google Analytics projects are being upgraded to Universal Analytics, so this module will not support the older ga.js implementation.

This module is mildly opinionated in how we instrument tracking within our front-end code. Our API is slightly more verbose than the core Google Analytics library, in the hope that the code is easier to read and understand for our engineers. See examples below.

If you use react-ga too, we'd love your feedback. Feel free to file issues, ideas and pull requests against this repo.

Installation

With npm:

npm install react-ga --save

With bower:

bower install react-ga --save

Note that React >= 0.14.0 is needed in order to use the <OutboundLink> component.

Usage

With npm

Initializing GA and Tracking Pageviews with react-router:

import ReactGA from 'react-ga';
ReactGA.initialize('UA-000000-01');
ReactGA.pageview(window.location.pathname + window.location.search);

With bower

When included as a script tag, a variable ReactGA is exposed in the global scope.

<!-- The core React library -->
<script src="https://unpkg.com/react@15.5.0/dist/react.min.js"></script>
<!-- The ReactDOM Library -->
<script src="https://unpkg.com/react-dom@15.5.0/dist/react-dom.min.js"></script>
<!-- ReactGA library -->
<script src="/path/to/bower_components/react-ga/dist/react-ga.min.js"></script>

<script>
  ReactGA.initialize('UA-000000-01', { debug: true });
</script>

Demo Code

For a working demo have a look at the demo files or clone this repo and run npm install npm start. Demo requires you to have your own TrackingID.

Upgrading from `1.x` to `2.x`

You can safely upgrade to 2.x as there are no breaking changes. The main new feature is that the underlying ga function is now exposed via the property ReactGA.ga. This can be helpful when you need a function that ReactGA doesn't support at the moment. Also, for that reason, it is recommended that you rename your imported value as ReactGA rather than ga so as to distinguish between the React GA wrapper and the original ga function.

Community Components

While some convenience components are included inside the package, some are specific to each application. A community curated list of these is available in the wiki: https://github.com/react-ga/react-ga/wiki/Community-Components. Feel free to add any you have found useful.

API

ReactGA.initialize(gaTrackingID, options)

GA must be initialized using this function before any of the other tracking functions will record any data. The values are checked and sent through to the ga('create', ... call.

Example

ReactGA.initialize('UA-000000-01', {
  debug: true,
  titleCase: false,
  gaOptions: {
    userId: 123
  }
});

Value	Notes
gaTrackingID	`String`. Required. GA Tracking ID like `UA-000000-01`.
options.debug	`Boolean`. Optional. If set to `true`, will output additional feedback to the console.
options.titleCase	`Boolean`. Optional. Defaults to `true`. If set to `false`, strings will not be converted to title case before sending to GA.
options.gaOptions	`Object`. Optional. GA configurable create only fields.

If you are having additional troubles and setting debug = true shows as working please try using the Chrome GA Debugger Extension. This will help you figure out if your implementation is off or your GA Settings are not correct.

ReactGA.set(fieldsObject)

Example

ReactGA.set({ userId: 123 });

Value	Notes
fieldsObject	`Object`. e.g. `{ userId: 123 }`

ReactGA.pageview(path)

Example

ReactGA.pageview('/about/contact-us');

Value	Notes
path	`String`. e.g. '/get-involved/other-ways-to-help'

See example above for use with react-router.

ReactGA.modalview(modalName)

A modal view is often an equivalent to a pageview in our UX, but without a change in URL that would record a standard GA pageview. For example, a 'contact us' modal may be accessible from any page in a site, even if we don't have a standalone 'contact us' page on its own URL. In this scenario, the modalview should be recorded using this function.

Example

ReactGA.modalview('/about/contact-us');

Value	Notes
modalName	`String`. E.g. 'login', 'read-terms-and-conditions'

ReactGA.event(args)

Tracking in-page event interactions is key to understanding the use of any interactive web property. This is how we record user interactions that don't trigger a change in URL.

Examples

ReactGA.event({
  category: 'User',
  action: 'Created an Account'
});

ReactGA.event({
  category: 'Social',
  action: 'Rated an App',
  value: 3
});

ReactGA.event({
  category: 'Editing',
  action: 'Deleted Component',
  label: 'Game Widget'
});

ReactGA.event({
  category: 'Promotion',
  action: 'Displayed Promotional Widget',
  label: 'Homepage Thing',
  nonInteraction: true
});

Value	Notes
args.category	`String`. Required. A top level category for these events. E.g. 'User', 'Navigation', 'App Editing', etc.
args.action	`String`. Required. A description of the behaviour. E.g. 'Clicked Delete', 'Added a component', 'Deleted account', etc.
args.label	`String`. Optional. More precise labelling of the related action. E.g. alongside the 'Added a component' action, we could add the name of a component as the label. E.g. 'Survey', 'Heading', 'Button', etc.
args.value	`Int`. Optional. A means of recording a numerical value against an event. E.g. a rating, a score, etc.
args.nonInteraction	`Boolean`. Optional. If an event is not triggered by a user interaction, but instead by our code (e.g. on page load, it should be flagged as a `nonInteraction` event to avoid skewing bounce rate data.
args.transport	`String`. Optional. This specifies the transport mechanism with which hits will be sent. Valid values include 'beacon', 'xhr', or 'image'.

ReactGA.timing(args)

Allow to measure periods of time such as AJAX requests and resources loading by sending hits using the analytics.js library. For more detailed description, please refer to https://developers.google.com/analytics/devguides/collection/analyticsjs/user-timings.

Example

Usage:

ReactGA.timing({
  category: 'JS Libraries',
  variable: 'load',
  value: 20, // in milliseconds
  label: 'CDN libs'
});

This is equivalent to the following Google Analytics command:

ga('send', 'timing', 'JS Libraries', 'load', 20, 'CDN libs');

Value	Notes
args.category	`String`. Required. A string for categorizing all user timing variables into logical groups.
args.variable	`String`. Required. Name of the variable being recorded.
args.value	`Int`. Required. Number of milliseconds elapsed time to report.
args.label	`String`. Optional. It can improved visibility in user timing reports.

ReactGA.ga()

The original ga function can be accessed via this method. This gives developers the flexibility of directly using ga.js features that have not yet been implemented in ReactGA. No validations will be done by ReactGA as it is being bypassed if this approach is used.

If no arguments are passed to ReactGA.ga(), the ga object is returned instead.

Example

Usage with arguments:

ReactGA.ga('send', 'pageview', '/mypage');

Usage without arguments:

var ga = ReactGA.ga();
ga('send', 'pageview', '/mypage');

ReactGA.outboundLink(args, hitCallback)

Tracking links out to external URLs (including id.webmaker.org for OAuth 2.0 login flow). A non-programmatic approach is found in the next section, by using an <OutboundLink> component.

Example

ReactGA.outboundLink({
  label: 'Clicked Create an Account'
}, function () {
  console.log('redirect here');
});

Value	Notes
args.label	`String`. Required. Description of where the outbound link points to. Either as a URL, or a string.
hitCallback	`function`. The react-ga implementation accounts for the possibility that GA servers are down, or GA is blocked, by using a fallback 250ms timeout. See notes in GA Dev Guide

`<OutboundLink>` Component

Outbound links can directly be used as a component in your React code and the event label will be sent directly to ReactGA.

Example

var ReactGA = require('react-ga');

render() {
  return (
    <div>
      <ReactGA.OutboundLink
        eventLabel="myLabel"
        to="http://www.example.com"
        target="_blank">
        My Link
      </ReactGA.OutboundLink>
    </div>
  );
}

Value	Notes
eventLabel	`String`. Required. Description of where the outbound link points to. Either as a URL, or a string.
to	`String`. Required. URL the link leads to.
target	`String`. Optional. To open the link in a new tab, use a value of `_blank`.

For bower, use the <ReactGA.OutboundLink> component.

ReactGA.exception(args)

GA exception tracking

Example

ReactGA.exception({
  description: 'An error ocurred',
  fatal: true
});

Value	Notes
args.description	`String`. Optional. Description of what happened.
args.fatal	`String`. Optional. Set to `true` if it was a fatal exception.

ReactGA.plugin.require(name, [options])

Require GA plugins.

Example

ReactGA.plugin.require('localHitSender', { path: '/log', debug: true });

Value	Notes
name	`String`. Required. The name of the plugin to be required. Note: if the plugin is not an official analytics.js plugin, it must be provided elsewhere on the page.
options	`Object`. Optional. An initialization object that will be passed to the plugin constructor upon instantiation.

ReactGA.plugin.execute(pluginName, action, [actionType], [payload])

Execute the action for the pluginName with the payload.

Example

ReactGA.plugin.execute('ecommerce', 'addTransaction', {
  id: 'jd38je31j',
  revenue: '3.50'
});

You can use this function with four arguments to pass actionType and payload along with executed action

Example

ReactGA.plugin.execute('ec', 'setAction', 'purchase', {
  id: 'jd38je31j',
  revenue: '3.50'
});

Development

Prerequisites

node.js
npm
npm install --global gulp

To Test

npm test

Submitting a PR

Always work on a new branch
Submit Pull Requests against master

Open a PR
Request code review
Complete code review with fixes
Merge the PR
Then, bump the version as below

The regenerated dist files should not be committed until the review has been R+'d and merged, since it's much easier to do the code review without the dist clutter getting in the way.

To Ship (i.e bump the version number)

git pull...
gulp build
mversion patch
git add .
git commit...
git push...
npm publish

Acknowledgements

Quite a lot of the code in this repo, came from webmaker-analytics.

awnali/react-ga

react-ga

React Google Analytics Module

Installation

Usage

With npm

With bower

Demo Code

Upgrading from 1.x to 2.x

Community Components

API

ReactGA.initialize(gaTrackingID, options)

Example

ReactGA.set(fieldsObject)

Example

ReactGA.pageview(path)

Example

ReactGA.modalview(modalName)

Example

ReactGA.event(args)

Examples

ReactGA.timing(args)

Example

ReactGA.ga()

Example

ReactGA.outboundLink(args, hitCallback)

Example

<OutboundLink> Component

Example

ReactGA.exception(args)

Example

ReactGA.plugin.require(name, [options])

Example

ReactGA.plugin.execute(pluginName, action, [actionType], [payload])

Example

Example

Development

Prerequisites

To Test

Submitting a PR

To Ship (i.e bump the version number)

Acknowledgements

Upgrading from `1.x` to `2.x`

`<OutboundLink>` Component