Show Menu
TOPICS×

Identify mobile devices

Most mobile devices accept browser cookies. However, in cases when devices do not accept cookies, another method is used to uniquely identify wireless devices.
Adobe has identified a number of HTTP subscriber ID headers that uniquely identify a majority of mobile devices. Those headers often include the device phone number (or a hashed version of the number), or other identifiers. The majority of current devices have one or more of the headers that uniquely identify the device, and all Adobe data collection servers automatically use those headers in place of a Visitor ID.
In a typical image request, a '1' in the path ( /b/ss/rsid/1 ) causes Adobe servers to return a gif image and to attempt to set a persistent visitor ID cookie ( AMCV_ or s_vi ). However, if the device is recognized as a mobile device based on the HTTP headers, a '5' is passed in place of the '1', which indicates that a wbmp format image should be returned and that our list of recognized wireless headers (not a cookie) should be used to identify the device.
The following table lists out the order of the ID methods used based on the return image type value ('1' or '5') in the path:
Setting ID method order
/1/
Default:
  • Custom visitor ID
  • Cookie
  • Subscriber ID Header
  • IP Address-UserAgent-Gateway IP Address
/5/ /5.1/ /5.5/
Device was identified as a wireless device, or /5/ was manually sent in the image request:
  • Custom visitor ID
  • Subscriber ID Header
  • Cookie
  • IP Address-User Agent-Gateway IP Address
You can also pass a '1' or a '5' in manual image requests, but be aware that these codes are mutually-exclusive, therefore always passing '5' does not leverage a cookie when it is supported. You can incorporate your own mechanism to determine if a device supports cookies, and if so, pass a '1' in the image rather than a '5'. The accuracy improvement in this situation is limited to the number of mobile devices supporting cookies.

Subscriber ID Headers

The subscriber ID method is generally more reliable than a cookie for user identification because of cookie deletion, cookie acceptance issues, and gateway cookie management issues.
You can improve changes of identifying a visitor by being added to the white list for the carrier that your mobile visitors use. To get access to the carrier's visitor ID, contact the carrier to add your domain to their white list. If you are on a carrier's white list, you also have access to subscriber ID headers that you may not otherwise be able to access.
The following list of headers is used to identify wireless devices. The algorithm for processing the headers is to
  1. extract the HTTP header key (the name of the header, such as,"X-Up-Calling-Line-ID")
  2. trim out all non alpha (A-Z and a-z) characters
  3. convert the header key to lowercase
  4. compare the end of the key to the ones in the following table to find a match:
Header
Type
Example
callinglineid
ID
X-Up-Calling-Line-ID: 8613802423312
subno
ID
x-up-subno: swm_10448371100_vmag.mycingular.net
clientid
ID
uid
ID
x-jphone-uid: a2V4Uh21XQH9ECNN
clid
ID
X-Hts_clid: 595961714786
deviceid
ID
rim-device-id: 200522ae
forwardedfor
ID or IP Address
X-Forwarded-For: 127.0.0.1
msisdn
ID or IP Address
X-Wap-msisdn: 8032618185
clientip
IP Address
Client-ip: 10.9.41.2
wapipaddr
IP Address
X-WAPIPADDR: 10.48.213.162
huaweinasip
IP Address
x-huawei-NASIP: 211.139.172.70
userip
IP Address
UserIP: 70.214.81.241
ipaddress
IP Address
X-Nokia-ipaddress: 212.97.227.125
subscriberinfo
IP Address
X-SUBSCRIBER-INFO: IP=10.103.132.128
For example "callinglineid" would match "X-Up-Calling-Line-ID" and "nokia-callinglineid." The header type tells us what to expect in the header. The order of header priority is listed here (if a "callinglineid" header is present it is used instead of "subno").
You can use Dynamic Variables to extract specific values from a header.