Analytics framework for iOS
AnalyticsKit
The goal of AnalyticsKit is to provide a consistent API for analytics regardless of the provider. With AnalyticsKit, you just call one logging method and AnalyticsKit relays that logging message to each registered provider. AnalyticsKit works in both Swift and Objective-C projects.
Supported Providers
- AdjustIO
- Apsalar
- Crashlytics
- Firebase Analytics
- Flurry
- Google Analytics
- Localytics
- Mixpanel
- mParticle
- Parse
- Mobile Center
- Debug Provider - shows an AlertView whenever an error is logged
- Unit Test Provider - allows you to inspect logged events
Unsupported Providers
The following providers are included but not supported. YMMV.
-
We’ve had a number of problems integrating the New Relic framework into the test app, so we can’t verify that events are logged correctly.
If you would like to add support for a new provider or to update the code for an existing one, simply fork the master repo, make your changes, and submit a pull request.
How to Use
Installation
- Download the provider’s SDK and add it to your project, or install via cocoapods.
- Add AnalyticsKit to your project either as a git submodule or copying the source into your project. In Xcode, only include AnalyticsKit.h/.m/.swift and any providers you plan to use.
- In your AppDelegate’s applicationDidFinishLaunchingWithOptions: method, create an array with your provider instance(s) and call
initializeProviders:.
NOTE: If you are gettings an error similar to target has transitive dependencies that include static binaries when using Crashlytics/Intercom add the following to the bottom of your Podfile:
pre_install do |installer|
# workaround for https://github.com/CocoaPods/CocoaPods/issues/3289
def installer.verify_no_static_framework_transitive_dependencies; end
end
Swift:
Initialize AnalyticsKit in application:didFinishLaunchingWithOptions:
AnalyticsKit.initializeProviders([AnalyticsKitFlurryProvider(withAPIKey: flurryKey)])
Depending on which analytics providers you use you may need to include the following method calls in your app delegate (or just go ahead and include them to be safe):
AnalyticsKit.applicationWillEnterForeground()
AnalyticsKit.applicationDidEnterBackground()
AnalyticsKit.applicationWillTerminate]()
If you’re using a legacy Objective-C AnalyticsKitProvider you will need to import that in your bridging header to make it available to Swift. You can find the name of the generated header name under Build Settings, Swift Compiler - Code Generation, Objective-C Bridging Header. Often named something like YourProject-Bridging-Header.h.
#import "AnalyticsKitNewRelicProvider.h"
Objective-C:
Make AnalyticsKit Swift classes available to your Objective-C classes by importing your Objective-C generated header. You can find the name of the generated header name under Build Settings, Swift Compiler - Code Generation, Objective-C Generated Interface Header Name:
#import "YourProject-Swift.h"
Initialize AnalyticsKit in applicationDidFinishLaunchingWithOptions
[AnalyticsKit initializeProviders:@[[[AnalyticsKitFlurryProvider alloc] initWithAPIKey:@"[YOUR KEY]"]]];
To log an event, simply call the logEvent: method.
[AnalyticsKit logEvent:@"Log In" withProperties:infoDict];
Depending on which analytics providers you use you may need to include the following method calls in your app delegate (or just go ahead and include them to be safe):
[AnalyticsKit applicationWillEnterForeground];
[AnalyticsKit applicationDidEnterBackground];
[AnalyticsKit applicationWillTerminate];
See AnalyticsKit.h for an exhaustive list of the logging methods available.
Channels
AnalyticsKit supports grouping analytics providers together into separate channels. If your primary providers is Flurry but you also want to log certain separate events to Google Analytics you can setup AnalyticsKit to log events following the instructions above and then setup a separate channel for Google Analytics as follows:
Swift:
// In didFinishLaunchingWithOptions you could configure a separate channel of providers
AnalyticsKit.channel("google").initializeProviders([AnalyticsKitGoogleAnalyticsProvider(withTrackingID: trackingId)])
// Then later in your code log an event to that channel only
AnalyticsKit.channel("google").logEvent("some event")
Objective-C:
// In didFinishLaunchingWithOptions you could configure a separate channel of providers
[[AnalyticsKit channel:@"google"] initializeProviders:@[[[AnalyticsKitGoogleAnalyticsProvider alloc] initWithTrackingID:trackingId]]];
// Then later in your code log an event to that channel only
[[AnalyticsKit channel:@"google"] logEvent:@"some event"];
Apple Watch Analytics
AnalyticsKit now provides support for logging from your Apple Watch Extension.
Supported Providers
Installation
- If you haven’t already done so, follow the installation steps above to add your provider’s SDK and AnalyticsKit to your project.
- Adding Provider’s API Key.
- Flurry: Follow steps outlined in Flurry’s Apple Watch Extension guide to add the API Key to the Extension’s info.plist.
Objective-C:
Initialize AnalyticsKit in awakeWithContext
AnalyticsKitWatchExtensionFlurryProvider *flurry = [AnalyticsKitWatchExtensionFlurryProvider new];
[AnalyticsKit initializeProviders:@[flurry]];
To log an event, simply call the logEvent: method.
[AnalyticsKit logEvent:@"Launching Watch App"];
Swift:
Import AnalyticsKit and any providers in your bridging header:
#import "AnalyticsKit.h"
#import "AnalyticsKitWatchExtensionFlurryProvider.h"
Initialize AnalyticsKit in awakeWithContext
let flurryProvider = AnalyticsKitWatchExtensionFlurryProvider()
AnalyticsKit.initializeProviders([flurryProvider])
To log an event, simply call the logEvent method.
AnalyticsKit.logEvent("Launching Watch App");