We have compiled a list of the most common questions received regarding our mobile SDK implementations. Please read through these questions before reaching out to our support team or your Customer Success Manager.
|Tag Management (WebView)||Tealium Collect (EventStream)|
There are many ways to debug and validate your Tealium mobile installation. Here are a few common ways:
If using Tag Management, we generally recommend using separate profiles for different platforms. However, this is more reliant on the vendor requirements for each platform. If requirements for iOS/Android align for the most part, using a single profile for mobile is possible.
We highly recommend keeping mobile and web traffic separate by utilizing separate profiles for mobile and web. It helps to streamline load conditions for tags that need to run only for mobile vs mobile and web. If a tag does need to run for both mobile and web, we recommend adding that tag with the same configurations to both profiles.
Visitor ID (tealium_visitor_id) is generated on the initial app launch after install and does not change. Visitor ID does change if the app in uninstalled and reinstalled on to the device.
All of the native SDKs implement offline queueing. When the network connection is lost, each tracked event is queued in persistent storage. When the network connection is restored the offline queue is processed. The queue capacity and dispatch expiration can be modified in the profile's mobile publish settings found within Tealium IQ.
Auto-tracking was removed from our SDKs to prevent performance and/or crash issues, but also because more events were tracked than most users needed. Even though it was removed, we do have future plans to bring it back in a limited, more refined, form.
We do have automatic lifecycle tracking for both Android and iOS.
The Tealium iOS and Android libraries currently support this functionality by allowing users to retrieve the entire visitor profile or attribute groups like audiences, badges, dates, booleans (flags), strings (properties), etc. References to the visitor service modules are listed below:
Deep linking is the process of launching an app at a specific entry point, which is usually triggered by a hyperlink from a web page, another app, email link, or a push notification. Deep linking is usually used in following scenarios:
The lifecycle variables provided within the Lifecycle Tracking Modules can be used to create variables and/or enrichments to identify a new install. If attribution tracking is desired as well, we have a module available in the Android and Swift SDKs that can add that information to the payload.
Tealium Trace assigns an ID to the events coming from your unique session and allows for refined debugging through a list of server-side events and actions. Learn more about Trace.
The Mobile Trace tool is available for use with our mobile SDKs. The Mobile Trace Tool enhances the trace feature by providing a QR code that is scannable by your device, enabling you to quickly view events coming from the Tealium Mobile SDKs.
Charles Proxy can also be used to start a trace using a Rewrite.
A manual trace can also be started using native code added to the app as outlined in the linked article.
Yes, for installations that use the Tag Management module: Adobe Target in a Mobile App without the Adobe SDK
For installation using the Collect module we advise using your own methods to make requests to Adobe’s API to retrieve the Target data. If desired, you can send that information in a tracking call to EventStream for analytics.