04-15-2015 10:07 AM - last edited on 01-04-2018 02:06 PM by kathleen_jo
A tutorial showing how to leverage UI Auto-tracking in the full mobile library and load rules
Table of Contents:
Tealium's Full Mobile Library has Auto Tracking which allows you to track almost everything in your app without implementing any custom tracking on anything in the app.
This tutorial will show you how to configure the UI Auto Tracking and configure your tags to only fire the actions you want to track in the app.
1.1 Full Mobile Library : Ensure you are using the full version of the Tealium Mobile Library in your app:
1.2 Configure UI Auto Tracking and the Mobile Companion : Ensure UI Auto Tracking and the Mobile Companion* is turned on in the Mobile Publish Settings and you have published this to dev, qa and prod in Tealium iQ for the profile you are using in your mobile app.
1.3 Enable Tealium Collect to store hits for your to debug : Ensure your app is using the Tealium Collect tag* and you can see live events firing through on your app.
*Ensure the Tealium Collect tag is has a load rule of 'all pages'. If Tealium Collect is not enabled on the 'prod' Tealium environment then you'll need to make sure you are using a build of the app which points to the 'dev' or 'qa' Tealium environment in order to debug the hits using Live Events.
2.1 Isolate your device using Trace : If you're debugging a production build of your app then you'll want to set up a Trace to isolate your device's hits. If you are debugging a dev or qa build of the app then you can skip to step 7.
In AudienceStream, go to Live Events under the Discover menu and add a new stream. Select Filter by Trace ID and make note of the Trace ID:
2.2 Open the Mobile Companion : In your app, open the Mobile Companion (if your developers have disabled the mobile companion in the production build of your app then ensure you have a build which has the mobile companion enabled)
2.3 Join the Trace in the Mobile Companion : Go to 'Tools' in the Mobile Companion and join the Trace:
3.1 View your actions in Live Events: If you are using an app build pointing to the dev/qa Tealium environment then you should only see your hits (unless other users are testing too) in Live Events. If your build is pointing to the prod Tealium environment then you should be using Trace to isolate only your hits:
3.2 Perform an action you want to track using a tag : Now that you can see what are doing in the app, the Tealium Mobile Library will try to grab any action you perform in the app. So, do something in the app, find the hit in Live Events and take a look at the data sources to see how you can isolate this hit.
For example, I will submit the value 'hello' in this form in my app:
When I debug this event in Live Events I can see there are a couple data sources which look useful for isolating submissions in this form:
I can see the 'link_id' is set to 'UIWindow : tapped' and also that the Tealium Library has generated a unique 'tealium_id' for this hit. All I need to do now is set a load rule against this hit to ensure my tag fires when someone performs this action.
4.1 Ensure your load rule for your tag includes this criteria : I'm going to add a load rule against my Google Analytics tag which will ensure the tag only fires on all 'view' events and when the 'tealium_id' equals 'b4a4af':
4.2 Set Data Sources for your UI Auto Tracked event : We know our tag is going to fire on all views and also our event. However, we want to make sure that we pass in some sensible values for the form submission so I'm going to use a 'set data values' extension to set some meaningful values:
These data sources are mapped in my Google Analytics tag:
4.3 Save and Publish : Once I've saved and published*, when I submit my forms I can see all 'view' events are tracked but also my form submission event is showing in Google Analytics:
*You may need to close and re-open your app and/or wait 5 minutes for your device to download the latest Tealium version which will reflect your changes.
4.3 You're done! You can now build more complicated load rules and extensions to track almost anything in your app. For example, a more advanced load rule might looks like this:
01-04-2018 02:00 PM - edited 01-04-2018 02:03 PM
01-05-2018 06:49 AM - edited 01-05-2018 06:49 AM
01-08-2018 10:59 AM - edited 01-08-2018 11:05 AM