App Tracking – Getting Started

You are here:
Estimated reading time: 2 min

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.

This guide is written for new users who are looking to learn on how to use the app tracking  functions in their account.
You need a verified email to start receiving incoming traffic data.

Using the App User Tracking System

Log into your account and head to Apps – Add New

You can also use the shortcuts at your home screen when logging into your account.
  • 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.

Dont worry if you use the wrong name, you can change it anytime you want.

Implementing the Traffic Reader

Once you successfully tagged your app, you receive an ID to relay usage data to your account through the Traffic Relay API.

Your relay ID will look something like this:

A-12345ABCDE
You can always check your Relay ID by checking your account and consulting you app’s details.

Relaying your data

To successfully relay data into your account, you need to make simple calls to the Traffic Reader API endpoint located in:

https://tgi.im/ap/tr/(YOUR_RELAY_ID)

This endpoint will accept the following arguments in order to successfully relay the data into your account’s analytics

Required Arguments

All of this data is required to relay data into your account.

Component Semantic Location

//Component semantic location
string tgi_loc

This is the semantic route to the component triggering the event.

Examples: “Root\Dashboard\UserProfile”, “Root\Options”, etc.

Event Type

//Event Type
string tgi_typ

This is the event type that helps you group events under one name.

Examples: “click”, “visit”, “submit”, etc.

Store Platform

//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.

Examples: “apple”, “google”, etc.

Device Type

//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.

Examples: “mobile”, “tablet”, “desktop”, etc.

Optional Parameters

The following optional parameters can help you further enhance your analytics.

Device Brand

//Device Brand
string tgi_dev_bnd

This is the brand of the device your app is running on.

Examples: “apple”, “google”, “samsung”, “htc”, etc.

Device Model

//Device Model
string tgi_dev_mod

This is the model of the device your app is running on.

Examples: “iPhone X”, “Samsung Galaxy 5”, “iPhone 5”, “Xperia”, etc.

Event Name

//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.

Examples: “Menu button”, “User registration submit”, “Store bundle 1”, “Share online”, etc.

Event Subname

//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.

Examples: “Purchase now”, “See details”, “Home user profile logoff”, “Share on Facebook”, etc.

Event Element

//Event Triggering Element Name
string tgi_elm

This is the element that triggers the event

Examples: “Button”, “Form”, “Link”, etc.
Was this article helpful?
Dislike 0