The Tealium Library for Android provides a lightweight and high performance installation of Tealium into all your Android applications. This integration provides rich data gathering capabilities allowing your application to leverage Tealium EventStream, AudienceStream, and DataAccess. By sending events to the Tealium Universal Data Hub, Tealium will process, enrich, act on your data, unlocking the marketing potential you demand.
Get a Demo
Join a live demonstration of Tealium's native support for Google to see how Tealium makes it easier to implement and enrich this part of your digital stack.
Supported Integration Types
Android can be integrated in the following ways:
  • Business Application Desktop applications, such as business intelligence or reporting tools, can also easily connect to Tealium services such as DataAccess.
  • Device-Based Delivery These connectors send data to the desired vendor or service directly from the client or device where the data is originating.
  • AudienceStream These connectors are hosted integrations within the Tealium platform utilizing AudienceStream. They receive data from the originating client or device, and send that data on to the desired vendor or service.
  • EventStream These connectors are hosted integrations within the Tealium platform utilizing EventStream. They receive data from the originating client or device, and send that data on to the desired vendor or service.
  • Installation Library Deploy Tealium to virtually any platform (web, connected device, IoT), language (java, ruby, perl), or content management service. Send any data to your desired end point vendor or marketing solutions.
  • Developer API Need deeper integration with a Tealium service? We offer a number of APIs providing richer configurability of your Tealium deployment.
  • Tealium Tool Tealium Tools is the playground for developers to integration with Tealium.
Supported Device Types
Connectors may be optimized to receive specific event attributes for select platforms. For example, a mobile phone would likely send a 'screen_name' event attribute, representing the name of the screen being viewed by the end user.
  • Web Browser These connectors expect to receive standard event attributes originating from a web browser, such as current_url, referring_url, page_name, page_category, and others.
  • Mobile Mobile Applications have a variety of conventional event attributes such as 'screen_width', 'screen_orientation', etc.
  • Your Server Tealium Collect can be deployed to any service or solution utilizing your favorite programming languages. This is the most 'generic' deployment.
  • Connected Devices Connected Devices are those that don't quite fit the mobile mold, such as connected set-top boxes (OTT), wearables, etc.
This integration offers these features
  • Collect Permits access to Tealium's EventStream and AudienceStream services. This feature allows for background event dispatching on certain devices and provides a lighter weight option to the Utag based Collect Tag.
  • Multiton Support This features allows for multiple instances of the Tealium library to be added to an application, including the ability to be used by an embedded by third-party framework.
  • Batch Dispatch Once a number of events equals or exceeds the remotely set limit, all queued dispatches will be delivered. This feature can be used to help limit how often dispatches are sent from a device.
  • Offline Tracking Events are queued until connection is re-established, then sent in the order they were originally recorded. The timestamp of when the event first occurred, and a special was_queued flag is set and made automatically available as part of the mobile data layer. This feature is useful for devices whose connectivity can come and go over time.
  • Tag Management This feature allows the use of the Utag library in a connected device, including the ability to process Load Rules, Extensions, and the capability of executing read-only (analytic) Tags. This feature allows devices to manipulate outbound dispatches before final delivery to vendors and access to web-based tags for vendors that may not yet have a mobile or IoT specific SDK or API endpoints.