Tealium Collect is the recommended solution for mobile, which uses HTTPS to send data to the Tealium Customer Data Hub. This approach ensures a light-weight footprint in your app by omitting the webview and leveraging the server-side power of Tealium EventStream and Tealium AudienceStream to activate your vendor integrations.
The data layer is a vendor-neutral and user-friendly representation of the activity you track on your digital properties. The device integration SDKs provide a standard set of built-in data layer variables.
Each platform has its own lifecycle module, which enables automatic tracking of app lifecycle events (launch, wake, sleep) and associated data.
A mobile installation of Tag Management requires a corresponding profile in iQ Tag Management that has been activated for mobile use. A mobile profile includes the built-in mobile data layer variables and additional publish settings to control some aspects of the Tealium SDK functionality without needing to deploy an app update.
Some data layer variables need to remain consistent throughout your app’s lifecycle. Instead of including these variables with every tracking call, use one of the storage solutions to set less volatile data layer variables.
Items added to persistent storage are kept for the lifetime of the app. For example, until the user uninstalls the app or manually clears the app’s data. Each persistent data variable is included in every tracking automatically.
Items added to volatile storage are kept until the app is cleared from memory, such as a force-close or restart. Each volatile data variable is included in every tracking call automatically. Volatile data is not stored on disk and does not contribute to the app’s disk usage footprint on the device.
If you upgrade from an older library (Java, Objective-C, or Swift 1.x) to a newer one (Kotlin or Swift 2.x) your persistent data is migrated automatically. The migrated data includes user consent preferences, lifecycle data, and the Tealium Visitor ID.