Mobile tracking allows a client to track the installs of a mobile application by passing the device ID and the device IP address to LinkTrust.

Mobile Tracking Methods

On the conversion when Pixel.track with Mobile Tracking is enabled for a campaign, then one of the following occurs:

Device ID (Best)

Using the Device ID and IP Address to track the install of a mobile app is the most accurate way to track installs.  In order to use this method, the Device ID must be appended to the click and pixel URLs.  Including the device's IP address is optional but increases accuracy.  If appending the IP address, it needs to be appended to the pixel URL if  the pixel is executed from a server.  If the pixel URL is executed from the user's mobile device, LinkTrust will capture the IP address automatically. 

The following is an example of a click and pixel URL with Device ID only:

• Click URL - http://...click.track?CID=1234&DeviceID=AA-BBBBBB-CCCCCC-D
• Pixel URL - http://...pixel.track?CID=1234&DeviceID=AA-BBBBBB-CCCCCC-D

The following is an example of a click and pixel URL where the IP address is also captured for additional accuracy:

• Click URL - http://...click.track?CID=1234&DeviceID=AA-BBBBBB-CCCCCC-D
• Pixel URL (executed from device) - http://...pixel.track?CID=1234&DeviceID=AA-BBBBBB-CCCCCC-D
• Pixel URL (executed from server) - http://...pixel.track?CID=1234&DeviceID=AA-BBBBBB-CCCCCC-D&DeviceIP=123.123.123.101

Note: The Device ID and IP Address will appear in the "Conversion Additional Data" column of the Transaction Details page.  A Device ID can be any of the following:

• IMEI numbers that come in a 17-digit or 15-digit sequences. The current IMEI format used is AA-BBBBBB-CCCCCC-D.
• An MEID is 56 bits long (14 hex digits). It consists of the following three fields: an 8-bit regional code (RR), a 24-bit manufacturer code, and a 24-bit manufacturer-assigned serial number.
• ESNs are often represented as 11-digit decimal numbers or 8-digit hexadecimal numbers.
• CDMA-based standards do not include any removable card, and the service is bound to a unique identifier contained in the handset itself. 
• Any uniquely generated value passed on on the click and returned on the pixel

Device IP Only (Good)

Using the Device IP Address to track the install of a mobile app is still a great way to track installs.  LinkTrust automatically captures the device IP at the time of click.  The device IP must then be appended to the pixel URL if the pixel is executed from a server.  If the pixel URL is executed from the user's mobile device, LinkTrust will capture the IP address of the device automatically to track installs. 

The following is an example of a click and pixel URL:

• Click URL - http://...click.track?CID=1234
• Pixel URL (executed from device) - http://...pixel.track?CID=1234
• Pixel URL (executed from server) - http://...pixel.track?CID=1234&DeviceIP=123.123.123.101

Note: The Device IP Address appended to the conversion URL always superseded the IP address captured by LinkTrust.

No Device ID or IP (OK)

If the device ID and IP address are not available, there is little you can do to track a mobile app install.  Consider configuring the campaign to use Standard Tracking, then do AFID Postbacks. The following is an example of the standard AFID postback pixel URL:

http://...pixel.track?CID=1234&AFID=1234