/README.md
Markdown | 368 lines | 269 code | 99 blank | 0 comment | 0 complexity | 74c080df1ab25e5e54acd298fd4aa376 MD5 | raw file
- TreasureData iOS SDK
- ===============
- iOS SDK for [TreasureData](http://www.treasuredata.com/). With this SDK, you can import the events on your applications into TreasureData easily. This library supports iOS 5 or later.
- Also, there is a more modern alternative SDK written in Swift [https://github.com/recruit-lifestyle/TreasureDataSDK](https://github.com/recruit-lifestyle/TreasureDataSDK).
- ## Installation
- There are several ways to install the library.
- ### CocoaPods
- [CocoaPods](http://cocoapods.org/) is needed to set up the SDK. If you've not installed it yet, install it at first.
- ```
- $ gem install cocoapods
- ```
- Next, add this line in your Podfile.
- ```
- pod 'TreasureData-iOS-SDK', '= 0.1.19'
- ```
- If you use the SDK in Swift, add this line to your Podfile.
- ```
- use_frameworks!
- ```
- Finally, execute 'pod install'.
- ```
- $ pod install
- ```
- ### Framework
- Download [TreasureData.framework](http://cdn.treasuredata.com/sdk/ios/0.1.19/TreasureData-iOS-SDK.framework.zip) and add it and `libz` library into your project.
- ## Usage in Objective-C
- ### Import SDK header file
- ```
- #import <TreasureData-iOS-SDK/TreasureData.h>
- ```
- ### Register your TreasureData API key
- ```
- - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
- [TreasureData initializeWithApiKey:@"your_api_key"];
- }
- ```
- We recommend to use a write-only API key for the SDK. To obtain one, please:
- 1. Login into the Treasure Data Console at http://console.treasuredata.com;
- 2. Visit your Profile page at http://console.treasuredata.com/users/current;
- 3. Insert your password under the 'API Keys' panel;
- 4. In the bottom part of the panel, under 'Write-Only API keys', either copy the API key or click on 'Generate New' and copy the new API key.
- ### Add events to local buffer
- ```
- - (IBAction)clickButton:(id)sender {
- [[TreasureData sharedInstance] addEventWithCallback:@{
- @"name": @"boo bar",
- @"age": @42,
- @"comment": @"hello world"
- }
- database:@"testdb"
- table:@"demotbl"
- onSuccess:^(){
- NSLog(@"addEvent: success");
- }
- onError:^(NSString* errorCode, NSString* message) {
- NSLog(@"addEvent: error. errorCode=%@, message=%@", errorCode, message);
- }];
- }
- ```
- Or, simply call `addEvent` method instead of `addEventWithCallback`.
- ```
- [[TreasureData sharedInstance] addEvent:@{
- @"name": @"boo bar",
- @"age": @42,
- @"comment": @"hello world"
- }
- database:@"testdb"
- table:@"demotbl"];
- ```
- Specify the database and table to which you want to import the events.
- ### Upload buffered events to TreasureData
- ```
- - (void)applicationDidEnterBackground:(UIApplication *)application {
- __block UIBackgroundTaskIdentifier bgTask = [application beginBackgroundTaskWithExpirationHandler:^{
- [application endBackgroundTask:bgTask];
- bgTask = UIBackgroundTaskInvalid;
- }];
- [[TreasureData sharedInstance] uploadEventsWithCallback:^() {
- [application endBackgroundTask:bgTask];
- bgTask = UIBackgroundTaskInvalid;
- }
- onError:^(NSString *code, NSString *msg) {
- [application endBackgroundTask:bgTask];
- bgTask = UIBackgroundTaskInvalid;
- }
- ];
- }
- ```
- Or, simply call `uploadEvents` method instead of `uploadEventsWithCallback`.
- ```
- [[TreasureData sharedInstance] uploadEvents];
- ```
- The sent events are going to be buffered for a few minutes before they get sent and imported into TreasureData storage.
- ### Start/End session
- When you call `startSession` method, the SDK generates a session ID that's kept until `endSession` is called. The session id is outputs as a column name "td_session_id". Also, `startSession` and `endSession` methods add an event that includes `{"td_session_event":"start" or "end"}`.
- ```
- - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
- {
- [TreasureData initializeWithApiKey:@"your_api_key"];
- [[TreasureData sharedInstance] setDefaultDatabase:@"testdb"];
- [[TreasureData sharedInstance] startSession:@"demotbl"];
- }
- - (void)applicationDidEnterBackground:(UIApplication *)application
- {
- [[TreasureData sharedInstance] endSession:@"demotbl"];
- __block UIBackgroundTaskIdentifier bgTask = [application beginBackgroundTaskWithExpirationHandler:^{
- [application endBackgroundTask:bgTask];
- bgTask = UIBackgroundTaskInvalid;
- }];
- [[TreasureData sharedInstance] uploadEventsWithCallback:^() {
- [application endBackgroundTask:bgTask];
- bgTask = UIBackgroundTaskInvalid;
- }
- onError:^(NSString *code, NSString *msg) {
- [application endBackgroundTask:bgTask];
- bgTask = UIBackgroundTaskInvalid;
- }
- // Outputs =>>
- // [{"td_session_id":"cad88260-67b4-0242-1329-2650772a66b1",
- // "td_session_event":"start", "time":1418880000},
- //
- // {"td_session_id":"cad88260-67b4-0242-1329-2650772a66b1",
- // "td_session_event":"end", "time":1418880123}
- // ]
- ];
- ```
- If you want to handle the following case, use a pair of class methods `startSession` and `endSession` for global session tracking
- - User opens the application and starts session tracking using `startSession`. Let's call this session session#0
- - User moves to home screen and finishes the session using `endSession`
- - User reopens the application and restarts session tracking within default 10 seconds. But you want to deal with this new session as the same session as session#0
- ```
- - (void)applicationDidBecomeActive:(UIApplication *)application
- {
- [TreasureData startSession];
- }
- - (void)applicationDidEnterBackground:(UIApplication *)application
- {
- [TreasureData endSession];
- }
- ```
- ### Detect if it's the first running
- You can detect if it's the first running or not easily using `isFirstRun` method and then clear the flag with `clearFirstRun`.
- ```
- - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
- :
- if ([[TreasureData sharedInstance] isFirstRun]) {
- [[TreasureData sharedInstance] addEventWithCallback:@{ @"event": @"installed" }
- database:@"testdb"
- table:@"demotbl"
- onSuccess:^(){
- [[TreasureData sharedInstance] uploadEventsWithCallback:^() {
- [[TreasureData sharedInstance] clearFirstRun];
- }
- onError:^(NSString* errorCode, NSString* message) {
- NSLog(@"uploadEvents: error. errorCode=%@, message=%@", errorCode, message);
- }
- ];
- }
- onError:^(NSString* errorCode, NSString* message) {
- NSLog(@"addEvent: error. errorCode=%@, message=%@", errorCode, message);
- }];
- }
- ```
- ## About Error code
- `addEventWithCallback` and `uploadEventsWithCallback` methods call back `onError` block with `errorCode` argument. This argument is useful to know the cause type of the error. There are the following error codes.
- - `init_error` : The initialization failed.
- - `invalid_param` : The parameter passed to the API was invalid
- - `invalid_event` : The event was invalid
- - `data_conversion` : Failed to convert the data to/from JSON
- - `storage_error` : Failed to read/write data in the storage
- - `network_error` : Failed to communicate with the server due to network problem
- - `server_response` : The server returned an error response
- ## Additional Configuration
- ### Endpoint
- The API endpoint (default: https://in.treasuredata.com) can be modified using `initializeApiEndpoint` class method. For example,
- ```
- [TreasureData initializeApiEndpoint:@"https://in.treasuredata.com"];
- [TreasureData initializeWithApiKey:@"your_api_key"];
- ```
- ### Encryption key
- If you've set an encryption key via `initializeEncryptionKey` class method, our SDK saves the events data as encrypted when called `addEvent` or `addEventWithCallback` methods.
- ```
- [TreasureData initializeEncryptionKey:@"hello world"];
- :
- [[TreasureData sharedInstance] addEventWithCallback: ....];
- ```
- ### Default database
- ```
- [[TreasureData sharedInstance] setDefaultDatabase:@"testdb"];
- :
- [[TreasureData sharedInstance] addEventWithCallback:@{ @"event": @"clicked" } table:@"demotbl"]
- ```
- ### Adding UUID of the device to each event automatically
- UUID of the device will be added to each event automatically if you call `enableAutoAppendUniqId`. This value won't change until the application is uninstalled.
- ```
- [[TreasureData sharedInstance] enableAutoAppendUniqId];
- :
- [[TreasureData sharedInstance] addEventWithCallback:@{ @"event": @"dragged" }
- database:@"testdb" table:@"demotbl"];
- ```
- It outputs the value as a column name `td_uuid`.
- ### Adding an UUID to each event record automatically
- UUID will be added to each event record automatically if you call `enableAutoAppendRecordUUID`. Each event has different UUID.
- ```
- [[TreasureData sharedInstance] enableAutoAppendRecordUUID];
- // If you want to customize the column name, pass it to the API
- // [[TreasureData sharedInstance] enableAutoAppendRecordUUID:@"my_record_uuid"];
- :
- [[TreasureData sharedInstance] addEventWithCallback:@{ @"event": @"dragged" }
- database:@"testdb" table:@"demotbl"];
- ```
- It outputs the value as a column name `record_uuid` by default.
- ### Adding the device model information to each event automatically
- Device model infromation will be added to each event automatically if you call `enableAutoAppendModelInformation`.
- ```
- [[TreasureData sharedInstance] enableAutoAppendModelInformation];
- :
- [[TreasureData sharedInstance] addEventWithCallback:@{ @"event": @"dragged" }
- database:@"testdb" table:@"demotbl"];
- ```
- It outputs the following column names and values:
- - `td_device` : UIDevice.model
- - `td_model` : UIDevice.model
- - `td_os_ver` : UIDevice.model.systemVersion
- - `td_os_type` : "iOS"
- ### Adding application version information to each event automatically
- Application version infromation will be added to each event automatically if you call `enableAutoAppendAppInformation`.
- ```
- [[TreasureData sharedInstance] enableAutoAppendAppInformation];
- ```
- It outputs the following column names and values:
- - `td_app_ver` : Core Foundation key `CFBundleShortVersionString`
- - `td_app_ver_num` : Core Foundation key `CFBundleVersion`
- ### Adding locale configuration information to each event automatically
- Locale configuration infromation will be added to each event automatically if you call `enableAutoAppendLocaleInformation`.
- ```
- [[TreasureData sharedInstance] enableAutoAppendLocaleInformation];
- ```
- It outputs the following column names and values:
- - `td_locale_country` : `[[NSLocale currentLocale] objectForKey: NSLocaleCountryCode]`
- - `td_locale_lang` : `[[NSLocale currentLocale] objectForKey: NSLocaleLanguageCode]`
- ### Use server side upload timestamp
- If you want to use server side upload timestamp not only client device time that is recorded when your application calls `addEvent`, use `enableServerSideUploadTimestamp`.
- ```
- // Use server side upload time as `time` column
- [[TreasureData sharedInstance] enableServerSideUploadTimestamp];
-
- // Add server side upload time as a customized column name
- [[TreasureData sharedInstance] enableServerSideUploadTimestamp:@"server_upload_time"];
- ```
- ### Enable/Disable debug log
- ```
- [TreasureData enableLogging];
- ```
- ```
- [TreasureData disableLogging];
- ```
- ## Troubleshooting
- #### With "Data Protection" enabled, TD iOS SDK occasionally crashes
- - If your app calls the SDK's API such as `TreasureData#endSession` in `UIApplicationDelegate applicationDidEnterBackground`, check if it's likely the app calls the SDK's API several seconds after iOS is locked. If so, please make other tasks that takes time and is called prior to the SDK's API run in background.
- ```
- - (void)applicationWillResignActive:(UIApplication *)application
- {
- dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_DEFAULT, 0), ^{
- // Some tasks that can take more than 10 seconds.
- });
- }
- ```
- ## Usage in Swift
- See this example project (https://github.com/treasure-data/td-ios-sdk/tree/master/TreasureDataExampleSwift) for details.