iOS In-Application Server-to-Server Conversion Tracking

Please follow the steps below to implement iOS in-application Server-to-Server conversion tracking.

Note: You must add the required parameters listed below to the call to implement this form of conversion tracking. Please note that there are differences between iOS devices version 6 and above and below version 6.

Required Parameters

Parameter Description
App Tracking ID The unique identifier for your campaign goal, used in the goal ID parameter.
WiFi MAC Address Used with iOS device versions prior to 6. Either this OR the IDFA should be passed in the HDID parameter. All Wifi MAC Addresses should be UPPER CASE with colon separators.
Advertising Identifier (IDFA) Hashed using SHA-1 or MD5 and used with iOS Versions 6+. Either this OR the WiFi MAC Address should be passed in the HDID parameter.
IP Address (UIP) The public IP address is the numerical label that is assigned to devices for host identification and location tracking. This is needed for matching app launches to clicks outside of in app inventory.

Please make sure that these parameters are in the proper format before they are sent.

Learn about required fields for iOS.

Note: We no longer require a UNIX timestamp, because we are asking that conversions be sent in real time. If you have an issue with sending real-time conversions, please contact your Account Manager or contact us to reach a trained support professional.

Integration Steps

Step 1: Use an HTTP Get to send conversion tracking data.

Conversion tracking data is sent to using an HTTP GET.


You must replace YOUR_APP_TRACKING_ID with your App Tracking ID, MD5_OR_SHA1_ID in the HDID parameter with the hashed Wifi MAC Address or IDFA and the DEVICE_IP_ADDRESS with the UIP.

For example, with App Tracking ID 12345, hdid aBc1234567891234567891234567891234567890 and UIP

Learn about the required parameters and how to properly format them.

Step 2: Check for an API response.

The Millennial server will return an HTTP response similar to the example below.

HTTP/1.1 200 OK
Server: nginx
Date: Fri, 19 Jul 2013 13:35:15 GMT
Content-Length: 0
Connection: close
Access-Control-Allow-Origin: *

Step 3: Test.

Follow the instructions here to test your iOS application to make sure that it’s ready for conversion tracking.

For More Information