This document provides information on how to use the InMobi Install API endpoint for negative targeting during new-user acquisition, and segment retargeting during user re-engagement campaigns.
This document is intended for advertisers who are directly sharing installs and segments data to InMobi.
Advertisers can provide install information to InMobi at the install endpoint.
The following parameters are required:
Parameter |
Required (Yes/No) |
Description |
|
No |
Time of install in long-UTC. If empty, it will be the time when InMobi received the ping. |
|
Yes |
Property ID as registered with InMobi. Click here for details on registering a property with InMobi. |
|
Yes |
Device identifiers adhering to the guidelines in the device ID section.
|
URL Format |
Notes:
|
URL Example |
|
JSON Response for Success |
|
JSON Response for Failure |
|
An advertiser can send up to 10 MB of bulk-install data in CSV format. The file must be zipped.
The CSV file needs to have at least one of the following headings based on the device ID type:
ida, gpId
Example:
gpId |
|
Please see below for the request structure of a multipart file upload.
URL Format |
|
URL Example |
|
Response Content Headers |
|
JSON Response for Success |
Note: The |
JSON Response for Failure |
|
Parameter Name |
Parameter Type |
Description |
|
String |
Identifier for advertiser without hashing. For iOS 6 and above, only. For more information, click here. |
Parameter Name |
Parameter Type |
Description |
|
String |
Google Play advertiser ID without hashing. Please see here for more information. |
Thank you for voting!