Motally launches 2-Way Communication, a powerful new feature that enables mobile app developers to make changes to existing tracking parameters (which includes tracking level and the conditions under which the data is sent), and to values in previously defined custom fields. This is all achieved through the web interface in their Motally account. We call this feature 2-Way Communication because now, it is no longer just the app that sends data to Motally, but now Motally can send data to the app, allowing developers to make changes and other updates remotely, without having to redeploy their application. This is especially useful in cases where developers have to through an app store approval process before launching their application.
TRACKING PARAMETERS
With Motally’s 2-Way Communication, developers can specify what level of data to track — whether it is at the action level, the error message level or the debug level. Tracking at the debug level is especially helpful for developers who have launched an application that might have some bugs to work out. In addition, developers can also specify other conditions under which the tracking data is sent. The following is a list of all the tracking parameter settings:
Device ID. This field specifies whether the other tracking data conditions applies to a unique device ID or is applied universally. The default (blank) applies changes to all devices.
Log level. This field specifies what level of tracking a developer wants to capture. “Debug & above” tracks down to the deepest (lowest) level and includes debug statements, error statements, and actions. “Error & above” tracks error statements and actions. “Action & above” tracks actions and higher.
Connection Level. This field specifies under which network conditions data is uploaded from devices. Choose any connection” to send data whenever users have a connection. Select “CDN only” to send data only when users are connected through the carrier data network. Choose “WiFi only” to send data only when users are connected through a WiFi network.
Minimum bundle size. This setting allows one to determine how often data is sent from users. For instance, if it is set to 5, the app will bundle the tracking messages and send them over when the count reaches 5.
Maximum storage size. This setting allows one to determine the number of tracking messages stored when the app is used but has no network connection. For instance, if it’s set to 100, up to 100 messages will be saved to be sent when the user is connected to a network.
CUSTOM DATA FIELDS
A developer who has created previously defined fields within their application can now make changes to the values for the data fields within their Motally account. Some examples when a developer might want to make changes to a custom field. include text changes, promotion codes, adding new features, and extending admin rights.
To illustrate, a developer can program a discount code field into an application and change the value for that code, based on a particular marketing campaign. Or, a developer can change the greeting on a text to go from “Hello” to “Hola”, depending on what country the game is being accessed. Truly, the possibilities are limitless, and is determined on the specific needs of each individual developer.
Device ID. Similar to the tracking parameters section, one can activate these custom fields on an individual user basis via the device ID field or submit a universal update, which is the default blank setting.
Custom Data Key. This is the name of the field that the application will request from the integrated Motally library.
Custom Data Value. This is the value that will be returned by the library when requested based on the aforementioned Custom Data Key.
With the announcement of our 2-way communication feature, Motally is once again leading the way to provide the most powerful, flexible tracking solution for mobile app developers.
