Once you have the Android library added to your app and have configured your mobile iQ Profile you are ready to validate your installation. The type of installation will determine the best method for validating.
We recommend using a build of your app configured for the "dev" environment rather than "prod" environment. This allows you to use the iQ Publish Environments to isolate your "dev" configuration from your "production" configuration. The environment is set in the Initialization part of your app's code.
This article covers the following topics related to validating your Tealium for Android installation:
You can use the Live Events feature of AudienceStream for the purpose of validating your mobile apps. Live Events will show tracking calls coming into Tealium in real-time and is the easiest way to verify that your mobile app is sending data to Tealium correctly.
For customers with an AudienceStream account, there are two ways that data will come into the Live Events service: (1) through the Tealium Collect Tag configured for mobile apps using Tag Management and (2) directly from the device for mobile apps using the Collect dispatch service. Read more about these mobile configuration options.
Access to Live Events is still available, but is limited to the "dev" environment.
If you enable this in a production environment you will be charged for the number of events Tealium has processed. Remember to disable these settings prior to a production release.
To send data to Live Events through Tag Management:
To send data to Live Events through the mobile Collect library:
Now when you launch and use your app the tracking calls can be monitored in Live Events.
Live Events will display event activity coming from all tracking sources, but you can create a filtered Stream of events based on any of the event attributes being passed. This can helpful when validating your mobile installation.
To create a filtered Stream for your mobile app:
tealium_library_nameequals (Custom Value) "Android"
The Stream condition can be based on any attribute that uniquely identifies events coming from your app.
Read more about Creating Streams.