Expand my Community achievements bar.

Join us January 15th for an AMA with Champion Achaia Walton, who will be talking about her article on Event-Based Reporting and Measuring Content Groups!
SOLVED

iPhone version and mobile screen size

Avatar

Level 2

In SiteCatalyst:

1.
iPhone (and possibly other phones) by dimension ‘Mobile Device’ are reported incorrectly.
For example a sample report for visits for a few days on our site shows:
Apple iPhone 1315685
Apple iPhone Simulator 12
Apple iPhone 5 3
Apple iPhone 4S 1

‘Mobile Device’ does recognize versions, but it is not correctly reported.

Is this something that can be fixed in SC?

2.
The dimension Mobile Screen Size is reported as:
Apple iPhone: 320 x 480
Apple iPhone 5: 640 x 1136
Apple iPhone 4S: 640 x 960

For 5 and 4S this is the correct physical device dimensions.
Is this input coming from lookup tables maintained by SiteCatalyst?
We would prefer the device w and h to be reported (CSS device independent pixels), as opposed to physical w and h. See http://www.mydevice.io/devices/ 
That is we want the device pixel ratio to be considered too. 
While this is something we can calculate ourselves in SC (since we are sending dpr in a context variable), it would be nice if it were available directly in SC.

Is this possible?

1 Accepted Solution

Avatar

Correct answer by
Level 8

Hi,

 

Here are answers to your questions question wise :

 

1)

This reporting depends upon the User Agent String. This runs essentially on the same principle as discussed in this forum post. Additionally you can also refer to this document and see if it helps.

 

2)

rax_s wrote...

 

2.
The dimension Mobile Screen Size is reported as:
Apple iPhone: 320 x 480
Apple iPhone 5: 640 x 1136
Apple iPhone 4S: 640 x 960

For 5 and 4S this is the correct physical device dimensions.
Is this input coming from lookup tables maintained by SiteCatalyst?

Yes this is correct.

rax_s wrote...

 

We would prefer the device w and h to be reported (CSS device independent pixels), as opposed to physical w and h. See http://www.mydevice.io/devices/ 
That is we want the device pixel ratio to be considered too. 
While this is something we can calculate ourselves in SC (since we are sending dpr in a context variable), it would be nice if it were available directly in SC.

Is this possible?

 

Currently this is not supported.

 

Thanks

Nikhil

View solution in original post

2 Replies

Avatar

Correct answer by
Level 8

Hi,

 

Here are answers to your questions question wise :

 

1)

This reporting depends upon the User Agent String. This runs essentially on the same principle as discussed in this forum post. Additionally you can also refer to this document and see if it helps.

 

2)

rax_s wrote...

 

2.
The dimension Mobile Screen Size is reported as:
Apple iPhone: 320 x 480
Apple iPhone 5: 640 x 1136
Apple iPhone 4S: 640 x 960

For 5 and 4S this is the correct physical device dimensions.
Is this input coming from lookup tables maintained by SiteCatalyst?

Yes this is correct.

rax_s wrote...

 

We would prefer the device w and h to be reported (CSS device independent pixels), as opposed to physical w and h. See http://www.mydevice.io/devices/ 
That is we want the device pixel ratio to be considered too. 
While this is something we can calculate ourselves in SC (since we are sending dpr in a context variable), it would be nice if it were available directly in SC.

Is this possible?

 

Currently this is not supported.

 

Thanks

Nikhil

Avatar

Level 2

Hi Nikhil,

Thanks for clarifying. Had a related question/request:

If I understood correctly, desktop monitor resolution is derived from the screen width x height sent from the browser in the pixel request. For mobile devices, this w x h is ignored while generating the screen sizes dimensions (instead UA inferred device + table based screen sizes are used).

The user agent seems to be invalid for most all iPhone requests in our SiteCatalyst data. We are unable to generate a good screen screen size report.

Is it a possibility that the screen width/height for mobile devices is also read from the w x h sent in the pixel request. From our data, this will probably give better results as compared to UA detection/screen size lookup. From my limited tests, the existing screen.height/width based JS code used for desktop monitor resolution also sends mobile w x h correctly in most cases.

Unfortunately we do not have evars/props set aside for screen width and height, to use the workaround given in the link you sent :(

Thanks,
Sriram