In order to provide robust reporting and attribution for your advertising campaigns, Vungle needs to track installs of your app. This way, we can make sure your campaigns are performing well, and driving quality traffic and users to your app. The most common way to send Vungle install information is through a 3rd party tracking solution
\Note : As of August 1, 2014, all apps being uploaded to the Google Play Store should use the Play Services Advertising ID in lieu of any other identifiers, or else risk ejection from the Play Store. See the Google Play Services Documentation for more details.
API Version 3
We have the same API end point for both the iOS and Android platforms, but each requires different parameters. The base endpoint is:
At a minimum, the request must contain your Vungle App ID, and a device ID of some kind. See below for the list of accepted parameters:
Required. The App ID listed in red on your application's page on the Vungle Dashboard. If your app isn't on the Dashboard yet, then be sure to add it.
The identifier for Advertising, a UUID provided by Apple for iOS devices since iOS 6. This is the preferred device identifier for iOS.
The Advertising ID, a UUID provided by Google Play Services 4.0+, compatible with Android 2.3+. This is the preferred device identifier for Android.
A parameter for when preferred device identifiers cannot be used.
Required. Setting conversion=1 means that Vungle will attempt to attribute the install. Setting conversion=0 means that Vungle will not attempt to attribute it.
Optional parameter for tracking. If trk=mat (MobileApp Tracking), the conversion parameter is required.
Required for Vungle installs. This is used across events such as clicks, installs and views, to help Vungle attribute installs.
Thus, in a typical case, for each install which your app registers, you will send a GET request to our endpoint of the form:
DEPRECATED: The Mobile API Versions 1 & 2 (for both Android and iOS) are no longer supported, along with MAC-based attribution.