Voxa Google Analytics
Just install from npm
npm install --save voxa-ga
Important! As of version 1.0, this plugin is designed to work with Analytic properties that are setup as Websites. Previously it was the opposite, working only with Mobile Analytics Properties.
trackingId: "UA-XXXXXX-X" // Your app's tracking idalexa: "UA-XXXXXX-X" // You can also specify platform specific key based on voxaEvent.platform.namegoogle: "UA-XXXXXX-X" // You can also specify platform specific key based on voxaEvent.platform.nameappName: "hamurabi" // The application name. If not provided, an attempt will be made to derive itappVersion: "1.1" // The applications current version number. If not provided, an attempt will be made to derive it.ignoreUsers: // An array of users that will be ignored. Useful for blacklisting dev or monitoring accounts from analyticssuppressSending: false // A flag to supress sending hits. Useful while developing on the websitesuppressSlots: 'phonenumber' // An array of slots that shouldn't be logged automatically. Use to remove PII slots.
What You Get
By attaching the plugin, for free you get the following
- Track users by their Alexa user id
- The paths of each response will be logged as a page view (e.g. Welcome.FirstTimeUser)
- Events will be logged to track each
- Intent (category: "Intents", action: "IntentName")
- State (category: "States", action: "state-name")
- Slot (category: "Slots", action: "slot-nmae", label: "slot-value")
- User timings will be logged for
- Request processing time (how much time your code takes)
- Each state's occupancy time
- The device's capabilities (e.g. AudioPlayer) are logged it the flash-version variable
- Session start/stop bookends
- The user's locale
- Exceptions (fatal or caught) are captured
- Health check events from dialog flow are suppressed. more details
ga object is attached to the
alexaEvent object, allowing you to log custom events.
Suppressing State Events
Sometimes smaller intermediary states are just not interesting to log. Suppress a state from logging as follows:
Log a custom event by invoking
.event on the
Have something to time? Use the
ga object. Remember that the request and each state is already timed for you.
Use the visitor object to get access to a universal analytics object.
The plugin will automatically send hits at the end of each request.