This article describes how to use the App Tracking functionality in your account. Using this is very easy and takes about 5-10 minutes to have it up and running.
Using the App User Tracking System
Log into your account and head to Apps – Add New
- Name your App. Use the name that will appear in the store where you publish it.
Click on “CREATE” to have your app ready for tagging.
Implementing the Traffic Reader
You will receive an ID to relay usage data to your account through the Traffic Relay API once you have created an App in your account.
Your relay ID will look something like this:
Relaying your data
To successfully relay data into your account, you need to make simple calls to the Traffic Reader API endpoint located in:
This endpoint will accept the following arguments in order to successfully relay the data into your account’s analytics
Component Semantic Location
//Component semantic location string tgi_loc
This is the semantic route to the component triggering the event.
//Event Type string tgi_typ
This is the event type that helps you group events under one name.
//Store Platform string tgi_plt
This is the store your app is being distributed in.
Helps you know what platform is the most profitable in terms of usage and income.
//Device Type string tgi_dev_typ
This is the type of device your app is running on.
Helps you categorize and prioritize development on certain popular devices.
//Device Brand string tgi_dev_bnd
This is the brand of the device your app is running on.
//Device Model string tgi_dev_mod
This is the model of the device your app is running on.
//Event Name string tgi_nme
This helps you further identify an event from the rest.
Use this to tag different actions in the same page or component.
//Event Subname string tgi_sub
This helps you when you have very similar buttons or actions that need even more granular organization among your analytics.
This is very useful when you have a screen with multiple interactable menus, buttons and sections.
//Event Triggering Element Name string tgi_elm
This is the element that triggers the event