Module for using the Flurry event tracking service.
To access this module from JavaScript, you would do the following:
var Flurry = require("ti.flurry");
Turns on additional logging. Defaults to false;
Turns on additional logging. Defaults to false.
Use this to log the user's assigned ID or username in your system after identifying the user.
Use this to log the user age after identifying the user. Valid inputs are 0 or greater.
Use this to log the user gender after identifying the user. Valid inputs are m for male and f for female.
This option is on by default. When enabled, Flurry will attempt to send session data when the app is exited as well as it normally does when the app is started. This will improve the speed at which your application analytics are updated but can prolong the app termination process due to network latency. In some cases, the network latency can cause the app to crash.
This option is off by default. When enabled, Flurry will attempt to send session data when the app is paused as well as it normally does when the app is started. This will improve the speed at which your application analytics are updated but can prolong the app pause process due to network latency. In some cases, the network latency can cause the app to crash.
This option is off by default. When enabled, Flurry will send session data over SSL when the app is paused as well as it normally does when the app is started. This has the potential to prolong the app pause process due to added network latency from secure handshaking and encryption.
Initializes your Flurry session. You must get your own apiKey from Flurry's website: https://dev.flurry.com/
Initializes your Flurry session. Enables Flurry to handle crash reporting. You must get your own apiKey from Flurry's website: https://dev.flurry.com/
NOTE: iOS only allows one crash reporting tool per app; if using another, use Flurry.initialize('
Use logEvent to count the number of times certain events happen during a session of your application. This can be useful for measuring how often users perform various actions, for example. Your application is currently limited to counting occurrences for 300 different event ids (maximum length 255 characters). You can also optionally pass in a dictionary of properties that will be recorded. Up to ten different keys can be specified in this dictionary, all of which must be serializable.
Use this version of logEvent to start timed event. You can also optionally pass in a dictionary of properties.
Use endTimedEvent to end timed event before app exists, otherwise timed events automatically end when app exists. When ending the timed event, a new optional event parameters dictionary object can be used to update event parameters. To keep event parameters the same, do not pass in properties.
Enables the Flurry agent to automatically detect and log page views. Flurry agent will create a delegate on your app to detect user interactions. Each detected user interaction will automatically be logged as a page view. This only needs to be called in your application once.
Rather than using the logAllPageViews method, you can manually detect user interactions. For each user interaction you want to manually log, you can use logPageView to log the page view.
This allows you to set the current GPS location of the user. Flurry will keep only the last location information. WARNING: If your app does not use location services in a meaningful way, tracking the user's location can result in Apple rejecting the app submission.
The passed in dictionary should contain the following keys:
See example.
Jeff Haynie and Dawson Toth
View the change log for this module.
Please direct all questions, feedback, and concerns to info@appcelerator.com.
Copyright(c) 2010-2013 by Appcelerator, Inc. All Rights Reserved. Please see the LICENSE file included in the distribution for further details.
Flurry is Copyright(c) 2010 by Flurry, Inc.
Usage of this module is subject to the Terms of Service agreement of Flurry, Inc. as well as your Terms of Service agreement with Appcelerator, Inc.