The goal of an App Download campaign is to generate installs at the lowest cost for the app you are promoting. As such, tracking your installs is very important to understand the efficiency and the success of your campaign.
Measurement and attribution is simple in online advertising because of the seamless browsing experience and the presence of cookies. The same, however, becomes slightly complex in the mobile advertising world mainly because of the app stores and the absence of cookies in between apps. Here is where a tracking platform comes in.
A tracking platform not only reports installs acquired from campaigns across ad networks, but also helps ad networks optimize campaigns performance.
Tracking app installs across multiple mobile ad networks requires technical integration with your preferred attribution partner. InMobi works with the best attribution partners in the world a.k.a, with our MTAP’s (Mobile Tracking and Attribution Partners). Integration with these partners has been certified by InMobi and advertisers using any of these attribution partners will benefit from this tight partnership. If you do not have a partner and want to track installs, InMobi provides you with our very own tracking platform.
Both MPATs and the InMobi tracking platform provide advertisers with an SDK that needs to be installed in the advertiser app. Please refer to the partner guidelines to integrate the SDK correctly. Pay special attention when you are doing android integration to ensure that the Referrer works correctly. Also, some partners, including InMobi, provide a non-SDK mode of integration via API’s.
After you install and verify the SDK, set up your InMobi campaign. InMobi only requires the landing page URL AKA the click to tracking URL from the attribution partner. Make sure that you choose the correct partner in the drop-down and paste the provided tracking URL.
Follow the below steps to set up your tracker:
Notes:
Support Center
$IDA: iOS Identifier for advertising.$GPID: Android Google play advertising ID$UDID: Android md5 of android_ID (being phased out)$O1: Android sha1 of android_ID (being phased out)$IMP_ID: Macro used to send across InMobi’s click ID.$APPOGRAPHIC_ID: Will be replaced with the Appographic segment ID only for ads served from Appographic ad groups. Else, it will be replaced with -1. This link captures the mapping of appographic IDs to Appographic segment names.$GEO_CC: Will be replaced with the country code. We follow the ISO 3166-1 alpha-2 country codes.$HANDSET_TYPE: Will be replaced by the device type (feature phone/smart phone/tablet).$CAMPAIGN_NAME: This parameter will be replaced by the campaign name.$ADGROUP_NAME: Will be replaced by the ad group name.$CREATIVE_NAME: Will be replaced by the ad name.$BLINDED_SITE_ID: Will be replaced by the blinded publisher ID. If the ad served is from an Appographic ad group, the publisher ID replacement will be -1>Please see below for meanings of the different integration statuses:
If your campaign is stuck at Not Verified, here are some possible reasons, and things you can do to move it to Verified.
All our MTAPs (Mobile Tracking and Attribution partners) use a combination of technologies to track and attribute an install to the correct network. The technologies include:
All our partners use a combination of the above technologies for matching an install to a click. We call this the Attribution Waterfall.
InMobi provides advertisers with an in-house conversion tracking platform that is not only easy to integrate, but is also free. Note that our in-house conversion tracker lets you track installs for the InMobi network alone. We do not support tracking installs across other ad networks. To integrate with the InMobi conversion tracking platform please go through the instructions here.
If you chose the InMobi in-house tracking solution, you do not have to worry about setting up tracking URLs and install postbacks. Our system does this for you. All you need to do is follow the integration guidelines and chose IAT while setting up the campaign. If the integration is correct, the verification should be done and you will be able to start the campaign in no time.
IAT uses all the attribution technologies available for tracking installs to make sure that no install in missed or over-attributed. These technologies include device Identifiers, Referrer (Android only), and fingerprinting (only when device Identifiers are not available).
The waterfall for IAT attribution is as follows:
iOS:
Android:
Attribution Window
IAT uses a 10-day attribution window for device based or Referrer matching and a 24-hour window for fingerprint matching.
InMobi works with multiple mobile attribution partners. Integration with these partners has been certified by InMobi. Advertisers using an MTAP partner will benefit from the tight integrations that have been established between the partners and InMobi. You can view all the benefits here.
Certifications are based on attribution methodology, performance optimisation features (for example, like latency reduction), advanced targeting feature compliance, operability and support.
Please contact MAT support ( support@mobileapptracking.com) for integration of your app with MAT’s SDK. MAT also supports API integrations for tracking installs and post install events. See here for their integration guide.
Please refer to the instructions provided here for setting up InMobi campaigns using MobileAppTracking. After setting up, you will have a tracking URL that needs to be used in the InMobi campaign set up. The next section describes what the tracking URL looks like, and what it does.
MAT’s InMobi tracking URLs will look something like this:
MAT allows InMobi passing custom parameters in the tracking link. These parameters are used by some clients to get reporting data on the parameters passed. Some of the common parameters used are: site ID, creative ID, campaign ID, and so on. This link describes all the parameters that can be added to the tracking URL.
For more information on the attribution logic used by MAT, please click here.
Please contact Kochava support (support@kochava.com) to integrate your app with Kochava’s SDK. Kochava also supports API integrations for tracking installs and post install events. Click here for their integration guidelines.
Refer to instructions provided here for setting up InMobi campaigns using Kochava. When the setup is complete, you will have a tracking URL that needs to be used during the InMobi campaign set up. The next section describes what the tracking URL looks like, and what it does.
Below are parameters that Kochava uses to send data. Anything sent to Kochava can be resupplied to InMobi in the form of a postback. Users of the Kochava interface can send any information they want on the click.
Kochava supports all possible Device Identifiers for the purpose of reconciliation because they work across various publishers. Please note the device Identifier in the server-to-server API makes calls using the device_id_type parameter. The default for Android will be android_ID and the default for iOS will be IDFA.
Kochava supports clients passing custom parameters in the tracking link. These parameters are used by some clients to get reporting data on the parameters passed. Some of the common parameters used are site ID, creative ID, campaign ID, and so on. For a description of all the parameters that can be added to the tracking URL, see here and then locate the Standard Click Parameters section
Kochava’s reconciliation system works in a waterfall format. The attribution for an install is made against candidate clicks in the following order of priority.
Kochava fingerprinting is only applied to clicks for which Device Identifier based attribution is not made, nor is Device Identifier information present in a click. Kochava does not apply fingerprint routines to those clicks that have Device Identifiers. This is an important differentiator, as it results in true, accurate attribution and does not result in false-positive attribution (which results in over-attribution and more money spent by the advertiser).
Attribution window: Kochava uses a 30-day window for device based matching and a 7-day window for fingerprint matching. However, clients can change this and create a custom matching window per network.
Please contact AD-X support to integrate your app with the AD-Xs SDK. To see their integration page, click here.
Please refer to these instructions on setting up campaigns with InMobi using AD-X. When the setup is complete, you will have a tracking URL that needs to be used during the InMobi campaign set up. The next section describes what the tracking URL looks like, and what it does.
The Ad-X tracking URL for InMobi will look like this:
AD-X allows InMobi to pass custom parameters in the tracking link. These are used by some clients to get reporting data on the parameters passed. Some of the common parameters used are site ID, creative ID, campaign ID, and so on.
InMobi can use subid2 to subid10 with the above clicks URLs to send custom parameter.
The format is a standard query string parameters. For example: <tracking_url>?subid2=<custom_param>&subid3=<custom_param>&…</custom_param></custom_param></tracking_url>
Please contact AppsFlyer support (support@appsflyer.com) to integrate your app with the Appsflyer SDK. To access their integration page, click here.
Please see here for instructions on how to set up a campaign with InMobi using Appsflyer. After the setup is complete, you will have a tracking URL that needs to be used in InMobi’s campaign set up. The next section describes what the tracking URL looks like, and what it does.
The AppsFlyer tracking URL for InMobi will look like this:
See here for more on how the AppsFlyer tracking link is structured.
Appsflyer supports InMobi passing custom parameters in the tracking link. These parameters are used by some clients to get reporting on the parameters passed. Some of the most common parameters used are: site ID, creative ID, campaign ID and so on.
This link describes all the parameters that can be added to the tracking URL.
Please contact TalkingData’s support for integration of your app with TalkingData’s SDK.
TalkingData’s tracking URL for InMobi is only a base URL (that is, short URL). They would like clients to append the InMobi device specific and network specific macros to the base URL.
The iOS base URL looks like: http://a.appcpa.net/ss/v1/click/V9QlI5
The Android base URL looks like: http://a.appcpa.net/ss/v1/click/1cscUt
Ensure to add the required device and impression ID parameters to the base URL, as indicated above.
Talking Data uses device IDs, first. If the match is not successful, then they use fingerprinting. If fingerprinting doesn't work, then will use IP plus timestamp. This is for both Android and iOS.
Please contact Adjust support (support@adjust.com) to integrate your app with the Adjust SDK. This is the link to their integration page.
To set up campaigns with InMobi using Adjust, look at these instructions. You must enable the InMobi module in Adjust before running the campaign. See here for the latest documentation. There is a section AdJust's special partners document that follows the panel in the dashboard
Since all of the modules are the same, the documentation focuses on the key particularities, and the special partners document will be extended a little to provide more detail on partner setup in general.
After the setup is complete, you will have a tracking URL that needs to be used in the InMobi campaign set up. The next section describes what the tracking URL looks like, and what it does.
Adjust’s tracking URL is a simple shortened URL. There is no template created for networks. They provide clients with the flexibility of sending tracking parameters appended to the base URL provided by the client.
Your tracking link will look like this: http://app.adjust.io/foobar.
Append the device ID parameters they support as well as the 'inmobi_click_id' to the above link.
AdJust supports InMobi passing as many custom parameters as wanted in the tracking link. These parameters are used by some clients to get reporting data on the parameters passed. Some of the common parameters used are site ID, creative ID and campaign ID.
This link describes all the parameters that can be added to the tracking URL.
The waterfall for Adjust attribution is as follows:
iOS:
Android:
Attribution window:
Adjust attribution windows are as follows:
Please contact apsalar support (support@apsalar.com) to integrate your app with the Apslar SDK. Please see their integration page.
After the setup is complete, you will have a tracking URL that needs to be used during the InMobi campaign set up. The next section describes what the tracking URL looks, and what it does.
Apsalar’s tracking URL for InMobi will look like this:
Apsalar supports InMobi passing custom parameters in the tracking link. These parameters are used by some clients to get reporting data on the parameters passed. Some of the common parameters used are site ID, creative ID and campaign ID and so on.
See here for a description of all the custom parameters that can be used by InMobi to pass data on click.
Although InMobi recommends using an MTAP for tracking your campaigns, we support clients using their own tracker, or a third party tracker. To run such campaigns:
If you select Others as a tracking option, you may not see downloads in our reporting. Also, InMobi will not be able to optimise your campaign.
If you do not want to track your campaign and still want to run your campaign with InMobi:
If you select Others as a tracking option, you may not see downloads in our reporting. Also, InMobi will not be able optimise your campaign.
