This document provides information on how to publish a custom event to InMobi.
This document is intended for advertisers who are directly sharing custom events with InMobi. Custom events include registrations and surveys, among others.
Advertisers can provide custom events information at the custom endpoint.
The following parameters are required:
Parameter |
Required (Yes/No) |
|
Yes |
|
Yes |
|
Yes |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
|
No |
URL Format: |
propertyId=propertyId&trackingPartner=trackingPartner&eventName=eventName&ida=ida&gpId=gpId&impId=impId&isLastClick=isLastClick&isViewThrough=isViewThrough&isReengagement=isReengagement&deviceIp=deviceIp&useragent=useragent&attributed=attributed&appId=appId&country=country&appVersion=appVersion&dnt=dnt&deviceName=deviceName&requestId=requestId&eventTime=eventTime&eventWeight=eventWeight |
JSON Response for Success |
|
JSON Response for Failure |
|
The .CSV file needs to have at least one of the following headings based on the device ID type:
ida, gpId
Example:
gpId |
|
URL Format |
http://advertiser-content.inmobiapis.com/tpce/v1/upload/events/custom?propertyId=propertyId&trackingPartner=trackingPartner |
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!