Tealium Learning Center

To integrate the Tealium iOS Library:   Add to Project with a Dependency Manager Add to Project Manually Initialize Track Views Track Events View Samples & Documentation Before Submitting to the App Store   0. Requirements - Xcode 7+ - iOS 8.1+ - Approximately +300k to an app's final .ipa file size * The framework IS bitcode compliant.      1. Add to Project with a Dependency Manager:   Cocoapods pod "TealiumIOS"   2. Add to Project Manually:   Add TealiumIOS.framework to your project Copy framework to project in the resulting dialog box In the Target's General: Embedded Binaries: options add "TealiumIOS.framework" * For Swift projects be sure to include the TealiumIOSBridgingHeader.h file and add it to the project's:Target:Build Settings: Swift Compiler: Objective-C Bridging Header option.  Make sure all paths are as expected under the projects: target: build settings   3. Initialize   In the Application Delegate or within a helper class setup method:    Swift let config = TEALConfiguration.init(account: "tealiummobile", profile: "demo", environment: "dev") guard let tealium = Tealium.newInstanceForKey("uniqueInstanceID", configuration: config) else { // Any additional failure response here return }   Objective-C // import area @import TealiumIOS; // within some setup method TEALConfiguration *configuration = [TEALConfiguration configurationWithAccount:@"tealiummobile" profile:@"demo" environment:@"dev"]; Tealium *tealiumInstance1 = [Tealium newInstanceForKey:@"uniqueInstanceID" configuration:configuration];     4. Track Views In any UIViewController's viewDidAppear method:   Swift // Basic Tealium.instanceForKey("uniqueInstanceID")?.trackViewWithTitle("someTitle", dataSources: [:]) // With optional data let optionalData = ["someKey":"someValue"] Tealium.instanceForKey("uniqueInstanceID")?.trackViewWithTitle("someTitle", dataSources: optionalData) // With optional array data let optionalData = ["someKey":["arrayValue1","arrayValue2"]] Tealium.instanceForKey("uniqueInstanceID")?.trackViewWithTitle("someTitle", dataSources: optionalData)   Objective-C // Basic [[Tealium instanceForKey:@"uniqueInstanceID"] trackViewWithTitle:@"someTitle" dataSources:nil]; // With optional data NSDictionary *optionalData = @{@"someKey":@"someValue"}; [[Tealium instanceForKey:@"uniqueInstanceID"] trackViewWithTitle:@"someTitle" dataSources: optionalData]; // With optional array data NSDictionary *optionalData = @{@"someKey":@[@"arrayValue1","arrayValue2"]}; [[Tealium instanceForKey:@"uniqueInstanceID"] trackViewWithTitle:@"someTitle" dataSources: optionalData];     5. Track Events In any method that triggers or responds to an event trigger   Swift // Basic Tealium.instanceForKey("uniqueInstanceID")?.trackEventWithTitle("someEvent", dataSources: [:]) // With optional data let optionalData = ["someKey":"someValue"] Tealium.instanceForKey("uniqueInstanceID")?.trackEventWithTitle("someEvent", dataSources:optionalData) // With optional array data let optionalData = ["someKey": ["arrayValue1", "arrayValue2"]] Tealium.instanceForKey("uniqueInstanceID")?.trackEventWithTitle("someEvent", dataSources:optionalData)   Objective-C // Basic [[Tealium instanceForKey:@"uniqueInstanceID"] trackEventWithTitle:@"someEvent" dataSources:nil]; // With optional data NSDictionary *optionalData = @{@"someKey":@"someValue"}; [[Tealium instanceForKey:@"uniqueInstanceID"] trackEventWithTitle:@"someEvent" dataSources:optionalData]; // With optional array data NSDictionary *optionalData = @{@"someKey":@[@"arrayValue1", @"arrayValue2"]}; [[Tealium instanceForKey:@"uniqueInstanceID"] trackEventWithTitle:@"someEvent" dataSources:optionalData];       6. Samples & Documentation   Sample Apps API Documentation 7. Before Submitting to the App Store The library contains slices which will permits running in the simulator. Unfortunately supporting the simulator architecture is not allowed by Apple when submitting to the app store.  When creating your archive / IPA, be sure to run one of the two available simulator library stripping scripts found in our Troubleshooting iOS Guide.  ... View more

This guide shows how to add Tealium to your Android Wear app to track user activity.  Table of Contents Placeholder Requirements Active Tealium AudienceStream account Completion of Tealium for Android Android Version 4.4, API Level 20 or higher (special version for Wear) Get the Code The code for the Tealium Android Wear library can be found on Github in the same repository as Tealium for Android. You must download and install the library before proceeding. Download: Tealium for Android The files specific to Android Wear can be found in tealium-android/Support/AndroidWear/. Handheld Add tealium.mobile-5.x.x.aar to your application's dependencies. No additional code is necessary. Wearable In the application's wear module add the tealium.wear-5.x.x.aar dependency. Subclass the Wear Application's subclass and add the TealumWear's initialization code in its onCreate function. public class WearApp extends Application { public static final String TEALIUM_MAIN = "INSTANCE"; // Instance name from main app @Override public void onCreate() { super.onCreate(); TealiumWear.createInstance( TEALIUM_MAIN, TealiumWear.Config.create(this) .setLogLevel(Log.VERBOSE)); } } The value of TEALIUM_MAIN must match the instance name used in the initialization of the main application. For example, if your main application is initialized with this line: Tealium.createInstance("my_app", config); You would change the line in the WearApp to this: public static final String TEALIUM_MAIN = "my_app"; Tracking Tracking on the wearable is similar to the handheld side. The only difference is in how to pass custom data to the tracking calls. The wearable side uses a DataMap() instead of a Map() : Tracking Views java final DataMap data = new DataMap(); // ... TealiumWear.getInstance(WearApp.TEALIUM_MAIN) .trackView("someView", data); Tracking Events java final DataMap data = new DataMap(); // ... TealiumWear.getInstance(WearApp.TEALIUM_MAIN) .trackEvent("someEvent", data); Samples & Documentation Sample App API Documentation   ... View more

Available Platforms Typical SDKs Multiple SDKs Agility Problem Tealium's Solution Enhance Not Replace Library Features Adding the Tealium Library Available Platforms The Tealium mobile team has been renamed to Devices Integrations and responsibilities have been expanded to include all OTT and IoT devices and language platforms.  See the Github Repos article for a full listing of all currently available libraries. Typical SDKs Each analytic vendor or other mobile service provider requires a static library, framework or SDK to be added to an application.  Code must then be added at key locations to permit the SDK to track the desired data points. Once an application is running, the vendor SDK will detect, package and deliver the tracking data point to the target vendor servers'. Reporting data is reviewed via the vendor's online dashboard (or other provided means). Multiple SDKs The same process as above is repeated for any additional third-party services.  Captured data points by various SDKs may overlap and at least one line of code would be required by each SDK for each tracking event, resulting in larger memory requirements and denser code to maintain. Agility Problem     To add, remove or edit these SDKs requires a new build and release of application code.  This can result in fragmentation of your app, for versions that may contain no further changes than those to your analytic or other third-party backend service. Tealium's Solution   Tealium's SDK provides the power of multiple SDKs with the size and performance of a single SDK by allowing remote configuration of the framework via Tealium's IQ Dashboard. Tags, or API Bundles, for third party services can be added, removed and edited at whim.  After publishing,  ALL versions of an application with the same account-profile-target will then make use of the updates. Enhance Not Replace Tealium is a Tag Management service, and with Tealium Collect, also a real-time response service designed to expand or interconnect services provided by other vendors. Detailed data analysis, reporting and storage is still managed through respective analytic vendor accounts and dashboards. Library Features The Tealium Android, iOS, and tvOS libraries all share the following features: Multiton Pattern Multiton Pattern Multiple instances of the Tealium library are now possible by assigning each instance a unique string identifier.  This will be useful in cases where an umbrella entity requires their own configuration and tracking setup that is separate from a subsidiary firm that is also using Tealium to track activity within an app. Additionally, the Android and iOS (not not tvOS) libraries have the following feature: Multiple Dispatch Services Dispatch Services These are different communications systems or protocols that the library can send data from and can be remotely enabled or disabled via the TiQ Dashboard - Mobile Publish Settings dialog box.  The following dispatch services are currently available: Collect (Android, iOS, tvOS) S2S Legacy (Android, iOS, tvOS) Tag Management (Android, iOS) Collect Service:  uses direct HTTPS calls to the Tealium Collect endpoint which can pass data to Live Events and AudienceStream.  When used with AudienceStream accounts it can also return visitor profile data.  Note: only Live Events available for non AudienceStream accounts, please consult an Account Manager for adding AudienceStream to an existing account. S2S Legacy Service:  also uses a direct HTTPS call, sending data to Tealium's older S2S system to trigger Server-to-Server functions. Tag Managment Service: uses the UTAG.js library within an unrendered webview instance and works identifically to Tealium's web based solution.  Certain tags will have no effect (such as displaying ads), but all analytics or read-only tags will work.  Additionally, Tag Management allows for Remote Command triggering of custom code, trigger conditions are set within a Custom Remote Command tag from TIQ. Adding the Tealium Library Getting Started with Android Getting Started with iOS Getting Started with tvOS ... View more

This guide shows how to add Tealium to your Apple TV app to track user activity.  Table of Contents Placeholder Requirements Before proceeding, ensure you have satisfied the following requirements: Active Tealium AudienceStream account Xcode 7 or higher tvOS 9.0 or higher 100KB available space in .ipa file size Bitcode compliant framework  Installation Tealium uses CocoaPods to install and manage dependencies. Add the following dependency to your Podfile: pod "TealiumTVOS" The code for the Tealium tvOS library is stored on Github. You must download and install the library. Download: Tealium for tvOS We recommend cloning the library (instead of downloading) to make it easier to update to future releases. Once the code is in place follow these steps to add Tealium to your project: Add TealiumTVOS.framework to your project Copy framework to project in the resulting dialog box In the Target's General: Embedded Binaries: options add TealiumTVOS.framework  Initialization Once the Tealium for tvOS is added to your project you are ready to start coding. You will need the following parameters to initialize the code: account - the name of your iQ account profile - the name of the mobile profile within your iQ account environment - one of "qa" or "prod" datasource - (optional) the data source key from UDH instance key - a unique name for your instance (multiple instances are supported) In the Application Delegate or within a helper class setup method, you will invoke a Tealium instance with the following code: Swift let config = TEALConfiguration.init(account: "ACCOUNT", profile: "PROFILE", environment: "ENV", datasource: "DATASOURCE") guard let tealium = Tealium.newInstanceForKey("uniqueInstanceKey", configuration: config) else { // Any additional failure response here return } Objective-C TEALConfiguration *configuration = [TEALConfiguration configurationWithAccount:@"ACCOUNT" profile:@"PROFILE" environment:@"ENV", datasource:@"DATASOURCE"]; Tealium *tealiumInstance1 = [Tealium newInstanceForKey:@"uniqueInstanceKey" configuration:configuration];  Tracking Tracking Views Every time a user opens or changes a screen in the app a tracking call should be made.  A view is tracked by calling trackViewWithTitle()  with two parameters: the name of the screen and (optionally) contextual view data. In any UIViewController's viewDidAppear method:  Swift Tealium.instanceForKey("uniqueInstanceKey")?.trackViewWithTitle(NSStringFromClass(self.classForCoder), dataSources: [:]) Objective-C [[Tealium instanceForKey:@"uniqueInstanceKey"] trackViewWithTitle:NSStringFromClass([self class]) dataSources:nil]; The screen name will be populated in the event data as the screen_title variable. Tracking Events All non-view activity should be tracked as an event. This is easily done by calling trackEventWithTitle() with two parameters: an event name and (optionally) contextual event data.  Swift Tealium.instanceForKey("uniqueInstanceKey")?.trackEventWithTitle("someEvent", dataSources: [:]) Objective-C [[Tealium instanceForKey:@"uniqueInstanceKey"] trackEventWithTitle:@"someEvent" dataSources:nil]; The event name will be populated in the event data as the tealium_event variable. Samples & Documentation Sample Apps API Documentation ... View more

In this situation, we will be using the the universal track call: Tealium.track(Object,Map<String,String>,String). In each fragment, override the onResume() event with the following code: //import com.tealium.library.Key; //import com.tealium.library.Tealium; @Override public void onResume() { super.onResume(); Tealium.track( null, Tealium.map( Key.SCREEN_TITLE, "fragment-name"), Tealium.EVENT_NAME_VIEW); } Tealium.map(String...) is a convenience function for creating Map<String, String> objects. Key.SCREEN_TITLE is a String constant with the value "screen_title", you may use what ever key here in its stead. Tealium.EVENT_NAME_VIEW describes the data as a view call. Now in order to filter out the auto-tracked view events, we should filter them out using the Mobile Library Manager Extension: This filter will suppress any auto-tracked view events from being sent off, and our manual calls will be sent off in their stead. ... View more