Setting the integration with Qmobi is carried out in two steps: creating a tracking link and setting the postback (names like callback, pingback can also be found).
The operation principle is as follows:
- We place the ads and attract users from the approved traffic sources.
- User clicks on Qmobi tracking link and he is redirected (302 Moved Temporarily or 307 Temporary Redirect) to client’s tracking link from it.
- Client’s tracking link directs user to Google Play Market or App Store.
- User installs an app.
- Client sends the information about app install to Qmobi (postback).
- In the event caused by user actions or events registered in the mobile application, information about them is transmitted to Qmobi.
Step 1. Creation of the tracking link.
It is necessary to provide us the link to route the traffic and notify us about supported parameters such as:
- Advertising campaign name / ID
- Ads group name / ID
- Ad name / ID
- Sub-id
- Other options for tracking the effectiveness of advertising campaigns
These parameters are usually transmitted for a convenient tracking of results in the client’s control panel.
Except the information on advertising campaign given above, two more parameters, that will be saved at user’s click and available for use in postback (passthrough - parameters), are also needed.
- Click ID - a unique id of a click. Always dynamic; a new, unique value is generated with every click of a user.
Macro {clickid} is used for a substitution. - Tracker — an internal tracker ID, used by Qmobi. Required for a correct postback intake and event tracking. May take several values, for example, voluum, Qmobi, or remain empty.
Macro {tracker} is used for a substitution.
All of these parameters can be placed at any part of the link, by client’s demand
Example:
http://youtracker.com/click/app5337823/?partner=qmobi&tracker={tracker}&transaction_id={clickid}&campaign={campaign}&adset={adset}&ad={ad}
All values indicated in {} brackets will be replaced when moving to the related information. For example:
http://youtracker.com/click/app5337823/?partner=qmobi&tracker=voluum&transaction_id=1020910306a7b8e9fcd410591cb184&campaign=203518&adset=177565423&ad=72142384720
Step 2. Setting the postback.
Postback (pingback, callback, s2s pixel) is a mechanism to transfer the data from a third party tracker, affiliate program (or from advert) to the tracking solution.
Qmobi supports 2 types of postback — Install Postback and Event Postback.
Technical requirements:
Request method: GET
The maximum response size: 5000
Successful response codes: 200
Error codes: 404, 500
2.1 Install Postback
Install postback is mandatory.
Sends the information that there was install after following the tracking link.
It has the following form:
http://tracking.qmobi.com/postback/{network_name}?tracker={tracker}&cid={clickid}&event_name=install&install_time={install-ts}&aid={android-id}&gaid={adid}&idfa={idfa}&connection={connection}&carrier={carrier}&device_id={device-id}
| Macro Name | Type | Description |
| network_name | required | name (or ID) of an external tracker, ad network or a client, given by Qmobi manager |
| tracker | required | internal Qmobi ID, sent in a tracking link at user’s click |
| clickid | required | click ID, sent in a tracking link at user’s click |
| install-ts | optional | installation time (unix-timestamp is recommended). User customization is available, if necessary. |
| android-id | optional | android device ID (if available, otherwise - skip) |
| gaid | optional | unique device ad ID on Android platform (if available, otherwise - skip) |
| idfa | optional | unique device ad ID on iOS platform (if available, otherwise - skip) |
| connection | optional | type of user connection (3G/4G, WIFI) |
| carrier | optional | mobile operator or ISP for the wifi-connection |
|
device-id |
optional | device ID in an external resource (your internal id) |
Example:
http://tracking.qmobi.com/postback/apsalar?tracker=qmobi&cid=0e3d564a-44e3-4a60-9070-071b92b6c475&event_name=install&event_time=1484578543&device_id=4ab4f6ca48ac6bd4f3a2f28b3d6540e4b38b97ea&ip=93.187.189.254&country=RU&aid=&gaid=245ed11d-2c86-43e6-9bf6-6739af30edc8
2.2 Event Postback
Sends the information on the in-app events, for example: registration, purchase, level achievement etc.
It has the following form:
http://tracking.qmobi.com/postback/{network_name}?tracker={tracker}&cid={clickid}&event_name={event-name}&event_time={event-time}&event_value={event-value}
| Macro Name | Type | Description |
| network_name | required | name (or ID) of an external tracker, ad network or a client, given by Qmobi manager |
| tracker | required | internal Qmobi ID, sent in a tracking link at user’s click |
| clickid | required | click ID, sent in a tracking link at user’s click |
| event-name | required | name of the event |
| event-time | optional | event time (unix-timestamp is recommended) |
| event-value | optional | any data on the event, string or json |
Example:
http://tracking.qmobi.com/postback/apsalar?tracker=qmobi&cid=0e3d564a-44e3-4a60-9070-071b92b6c475&event_name=register&event_time=1484578648&event_value={"user_id":1238326, "is_first_registration":1}