This article shows how to enable a profile to be used for a mobile application installation.This mobile profile will be used to remotely manage the settings and vendor tracking deployed to your app.
Before you proceed with the following guide you need to create a new profile, appropriately named for its intended mobile app eg. "mobile-ios". Follow the guide Creating a Profile to create a new profile and then return here.
Mobile profiles are for use with an installation of one of the following mobile application platforms:
By default, profiles in your iQ account are configured for use on a website, but any profile can be activated for use within a native mobile installation. To activate a profile for use on mobile:
The standard mobile variables will be added to the profile and available in the Data Layer tab for use with Tags and Extensions.
The Profile can now be used in your mobile app integration by referencing the account name, profile name, and publish environment.
Your mobile Profile will now be used to adjust configuration settings regarding the behavior of your mobile installation. To adjust mobile configuration settings:
5. Click Save then complete the Save/Publish.
The next time your mobile app is loaded the new configuration will be detected and applied.
|Tag Management||Enables mobile tag management (utag.js runs in a webview).|
|Tealium Collect||Enable native mobile tracking (data sent directly to Tealium EventStream). Set to OFF if you enabled Tag Management.|
|Send Batch Data after every||Allows you to set the number of events that need occur before a those events are sent. Entering a value of 0 or 1 essentially turns off batching. The default value is set to 1.|
|WiFi only Sending||If enabled, events are only sent when the user's device is connected to a WiFi. The default value is OFF.|
|Battery Saver||By enabling ON, data will only be sent when the device is not in power saving mode (iOS: 20% battery, Android: 15% battery), or in the case of iOS, when the device is also not charging. The default value is ON.|
|Dispatch Expiration||Specify how long (in days) the data persists in the app if no data has been sent back. A value of -1 means there is no dispatch expiration. The default value is set to -1. Dispatch expiration is also applied to events queued due to WiFi only Sending or Battery Saver settings.|
|Minutes Between Syncronization||Number of minutes between configuration checks (checks occur at launches and wakes). The default value is 15.0.|
|Queue Capacity||Number of events and views to store on the device until ready to send (0 = no offline dispatching, -1 = no limit). The default value is -1.|
|Set Debugging Log Level||
Allows you to enable logging. The "Default" setting sets the log level to match the "Environment" setting in your configuration. Any other setting here will override that logic. Options: