Postback URL
This is also known as “callback URL” and it is a type of URL that the third party or advertiser uses to send conversion-related data to the Mintegral platform after attributing a conversion to it.
Postback Types
There are two types of postbacks:
| Type | Description | Example |
|---|---|---|
| installation | Postback after app activation, commonly used for installation statistics | http://postback.mintegral.net/install?campuuid={uuid}&clickid={click_id}&idfa={idfa}&type=s2s&install_time={install_time} |
| Event | Postback after a specific event trigger, commonly used for event statistics. A postback supports only one event, but can be sent multiple times to count multiple events | http://postback.mintegral.net/event?campuuid={uuid}&clickid={click_id}&idfa={idfa}&type=s2s&event_time={event_time}&event_name={event_name} |
Postback Parameters
The following are some commonly used postback parameters on the Mintegral platform:
| Parameter | Required | Description | Example |
|---|---|---|---|
| clickid | Yes | Mintegral Click id defined by the Mintegral platform | mtg0a1b2c3d4e5f6g7h8i9j1x2y |
| campuuid | Yes | Mintegral Promotion id defined by the Mintegral platform | game_ios_us_mtg |
| idfa | Yes, in some cases | Required for iOS | 3E0046F7-8BD4-4F3E-9F91-358B137D2BF0 |
| md5_idfa | Yes, in some cases | IDFA MD5 encryption (32-bit lower case) | 77d06cb28c1771e8019be4f4fb6e1938 |
| gaid | Yes, in some cases | Required for Android (not in China) | 7268ceb0-5411-4004-b7cb-bd1fee4b6277 |
| md5_gaid | Yes, in some cases | GAID MD5 encryption (32-bit lower case) | 7c687d7812ae6ca319aecea51d0d7750 |
| imei | Yes, in some cases | Required for Android (in China) | 869634020728636 |
| md5_imei | Yes, in some cases | IMEI MD5 encryption (32-bit lower case) | ed0427f06978ac06d73e2d6f2049aa9d |
| devid | Yes, in some cases | Required for attribution based on Android ID | d0d4845ae4495a83 |
| md5_devid | Yes, in some cases | ANDROID ID MD5 encryption (32-bit lower case) | 1ebf70337adb6df4b70300edc27c24c8 |
| mac | Yes, in some cases | Required for attribution based on MAC | 10:2A:B3:D1:52:F4 |
| md5_mac | Yes, in some cases | MAC MD5 encryption (32-bit lower case) | d53e994cce18ab87fdd25d155544532f |
| oaid | Yes, in some cases | Required for attribution based on OAID | fdcfebbf-5ebb-4958-35fe-cbdf74fd2fb3 |
| md5_oaid | Yes, in some cases | OAID MD5 encryption (32-bit lower case) | a27d1dda70b946cdb940ead82f01dd63 |
| pl | No | OS platform | android |
| os | No | OS version | 8.0.1 |
| device | No | Device model | Mi-4c |
| ip | No | IP | 59.189.187.99 |
| country | No | Country code | CN |
| app_version | No | App version | 1.1.2 |
| type | No | Name of third party or advertiser | s2s |
| install_time | No | Installation activation timestamp, only used for installation postback | 1486088825 |
| event_time | No | Event trigger timestamp, only used for event postback | 1486088825 |
| event_name | Yes, in some cases | Event name, only used for event postback | Purchase |
| event_value | Yes, in some cases | data related to the event, only used for event postback | 1.90 |
| currency | Yes, in some cases | data related to the event, only used for event postback.See the enumeration description for possible values | USD |
Important Parameter Description
1. currency
This enumeration defines a list of supported currency codes. Each currency code represents a specific legal tender.
| Enum Value | Description |
|---|---|
CNY | Chinese Yuan - The legal currency of the People's Republic of China |
USD | United States Dollar - The legal currency of the United States |
EUR | Euro - The official currency of the member countries of the European Union |
JPY | Japanese Yen - The legal currency of Japan |
GBP | British Pound Sterling - The legal currency of the United Kingdom |
| ... | ... |
Postback Direction
| Direction | Description | Example |
|---|---|---|
| Configure within the tracking URL | For advertisers integrated through S2S or several third parties; specify a parameter to configure the postback URL (pay attention to URL-encoded, see appendix tool). When click reporting, known parameters such as {uuid}, {click_id}, and device id will be passed with their real values | https://www.advertiser.com/click? some_params={params}& callback=http%3A%2F%2Fpostback.mintegral.net %2Finstall%3Fcampuuid%3D{uuid} %26clickid%3D{click_id} %26idfa%3D{idfa} %26type%3Ds2s%26install_time%3D%7Binstall_time%7D |
| Configure on advertiser’s server | For advertisers integrated through S2S | Defined by the advertisers’ technical developer |
| Configure via third party | Defined by the advertisers’ technical developer | No additional configuration needed for third parties like AppsFlyer, Adjust, etc. |