1.

Install Tracking using Custom Dimension:

Steps defined to enable custom dimension on GA and in App level.

1. Add User Level Custom Dimensions in a GA property - There will be mainly two
user level Custom Dimension added to a GA property to track referral tracking
namely,
a. Install_Source_Encoded - It will have a user level scope.
b. Install_Source_Decoded This will also have user level scope and will act as
a proxy for Install_Source_Encoded.
2. Install referrer information for any android device can be fetched by extending
broadcast receiver and tracking install referrer information in the extended broad
cast receiver class.
3. The above install referrer information provides campaign related information like
Campaign Source, Campaign Medium, Campaign Name etc
4. Client has to pass Campaign Source (utm_source) for an ad campaign to a custom
dimension, namely Install_Source_Encoded, using the following Code snippet
corresponding to a custom dimension:
String dimensionValue = "SOME_DIMENSION_VALUE (Campaign Source)";
tracker.set(Fields.customDimension(1), dimensionValue);
5. The GA tracker will start sending all data related to each campaign source.
6. Install_Source_Decoded custom dimension can be created to create a proxy for
Install_Source-Encoded custom dimension. Code snippet for Install_Source_Decoded
need not be added at client level. Mapping between Install_Source_Encoded and
Install_Source_Decoded has to be imported to GA using Data Import option under a
GA property.
7. Custom Reports is to be used to see reports based on Custom Dimensions. Custom
Report based on a Custom Dimension can be created for getting User based Metric
level data (for example Sessions, Screen View, Average Session Duration etc).
8. Filter and Views can also be created for above Custom Report to get drilled down
data based on Filters and Views. For example in Gaana Mini app, view level filter can
be used to get install referral based data for all the Gaana mini apps.
9. AppStore_Referrer as hit level( Ad of which app, can be imported from DFP report)



2. Install Tracking
3. Uninstall Tracking:
4. Cross Promotion on iOS:

5. Cross Promotion on Android
1.
For ad promotion at Native ad position of any app:
1. Any app installed on a device will internally find out the install version
of other TOI group apps. For example a device with a TOI
app(cross promotion feature implemented in it) will internally find
install version of all other TIL group apps on the device.
2. Thus, for example, if a device has latest version of TOI and Magic Brick
and some older version of go cricket and ET installed, then TOI
app will internally find out install version of all these 4 apps and
send these install status as custom parameter of any DFP native
ad call. In this case, following array of string, namely: {TOI_Latest,
MagicBrick_Latest, gocricekt_Update and ET_Update} will be
sent as Custom Parameter of all DFP native ad calls.
3. Based on the custom parameter sent to DFP native ad call, DFP will
take ad serving decisions in the following manner:
For apps which are not installed in the device no signal for
these apps will be sent as custom parameter to DFP and
thus DFP will show install ads for these apps. In this case, ad
will direct to app store to install the app. For example, since
Gaana was not installed in the device, ads for Gaana will be
shown to the users.
For AppName_Latest signals(in this case TOI_Latest and
MagicBrick_Latest) - DFP will pass a deep link to a specific
content of TOI and Magic Brick
For gocricekt_Update and ET_Update signal DFP wills serve ad
content with update message for goCricket and ET. This will
help in getting all users to latest version of apps
4. This will help in optimised serving of ads and DFP will serve ads only
for those apps which are not installed.
For ad promotion at grid position of Gaana mini apps:
1. Gaana mini will have 2 types of ads : Ads at Native ad position(similar
to any other app) and Ads at rectangular grid positions(ads will
come instead of a playlist or album)
2. Ads serving for Native ad position will follow same rule as followed by
any other app. Here TIL group adds like Gaana, TOI, ET, gocricket
etc will be served along with any other external ads as decided by
ad team. Till the time gaana app is not installed
3. Ad serving at rectangular grid position will show ads for Gaana and
Gaana mini.
4. Gaana mini app will internally find out install status of other Gaana
mini apps. For example, if a device has Latest version of Love Song
Hindi, Hindi Sad Songs and Top Ghazals installed, then from a
Kishore Kumar Hit Songs app, array of strings,
namely, {LoveSongHindi_Latest, HindiSadSongs_Latest, TopGhaz
als_Update} will be sent as custom parameter to any DFP ad call
for grid ads.
5. Based on point 4, DFP will serve ads for Old Hindi Song, Classical Hindi
Love Songs and any other mini aps not installed in the device.
Further, for apps with Latest install version(in this case Love Song
Hindi, Hindi Sad Songs, Top Ghazals), DFP will serve ad with deep
link to Gaana app with content similar in nature to apps with
latest version apps.
There is one concern if you have multiple ad slots for cross promotion same
app may be repeated with