Tealium Collect is a lightweight data collection module that sends user events from your mobile app to the Tealium Customer Data Hub. The Tealium Collect module allows you to integrate third-party vendors as server-side connectors instead of as installed SDKs.
Tealium Collect uses event batching and other power-saving techniques to provide the following benefits to mobile applications:
Tag Management is the module that enables Tealium iQ Tag Management within your mobile app. This client-side solution uses a hidden webiew to run standard web-based vendor tags in your app. Use the Tag Management module to integrate with third-party vendors that do not support a server-side API.
The data layer is a vendor-neutral and user-friendly representation of the activity you track on your digital properties. In addition to the standard built-in data layer variables provided by each platform installation, you will populate custom data layer variables with dynamic values from your app.
Remote commands are a client-side solution for triggering functionality in your native app. Use remote commands for custom native features or to integrate with third-party SDKs. Configure remote commands with a JSON file or a remote command tag in Tealium iQ Tag Management.
Each platform has its own lifecycle module, which enables automatic tracking of app lifecycle events (launch, wake, sleep) and associated data.
An app that uses the Tag Management module must have 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 settings for the Tealium SDK that can be adjusted 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.
Data layer variables added to persistent storage are kept until the user uninstalls the app or manually clears the app’s data. Each persistent data variable is included in every tracking automatically.
Data layer variables 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.