Add a "device category" property

Amplitude currently lacks a “device category” property to provide a top-level split of Mobile VS Desktop VS Tablet. There’s a hacky way to get to this (https://community.amplitude.com/data-instrumentation-57/how-to-create-a-computed-property-2303), but this absolutely feels like a property that should be out-of-the-box and managed by Amplitude.

Thanks!

Find more posts tagged with

Implemented

Status: Completed

Comments

dangrainger

Sorry, pasted incorrect link in the above. Here’s the correct reference…

Jonathan Callahan

Here’s how we set this up as a derived property, couldn’t find anything else already written up on the forums. Not perfect but it appears to work. Still would love to see this provided by Amplitude.

IF(<br />	<device family property>  contains (<br />		'tab',<br />		'ipad',<br />		'kindle'<br />	),<br />	'tablet',<br />	IF(<br />		<OS property>  contains (<br />			'mobile'<br />		),<br />		'mobile',<br />		IF (<br />			<OS property>  contains (<br />				'none'<br />			),<br />			'unknown',<br />			'desktop'<br />		)<br />	)<br />)

JennRu

This feedback has been submitted to Amplitude product team, I equally hope they can build out this new OOTB user property this year 🤞🏼

Similar to Jonathan Callahan’s comment above, I built this derived property based on device family groupings as well

  IF(<br />    OR(<br />      PROPERTY('device', 'amplitude_user') contains 'phone', <br />      PROPERTY('device', 'amplitude_user') contains 'ios', <br />      PROPERTY('device', 'amplitude_user') contains 'android',<br />      PROPERTY('device', 'amplitude_user') contains 'symbian',<br />      PROPERTY('device', 'amplitude_user') contains 'tizen',<br />      PROPERTY('device', 'amplitude_user') contains 'mobile'<br />    ), <br />    'mobile', <br />    IF(<br />      OR(<br />        PROPERTY('device', 'amplitude_user') contains 'windows', <br />        PROPERTY('device', 'amplitude_user') contains 'linux', <br />        PROPERTY('device', 'amplitude_user') contains 'mac',<br />        PROPERTY('device', 'amplitude_user') contains 'chrome os',<br />        PROPERTY('device', 'amplitude_user') contains 'chromium os',<br />        PROPERTY('device', 'amplitude_user') contains  'WebOS',<br />        PROPERTY('device', 'amplitude_user') contains 'ubuntu'<br />      ), <br />      'desktop', <br />      IF(<br />       OR(<br />       PROPERTY('device', 'amplitude_user') contains 'tablet',<br />       PROPERTY('device', 'amplitude_user') contains 'ipad',<br />       PROPERTY('device', 'amplitude_user') contains 'note',<br />       PROPERTY('device', 'amplitude_user') contains 'xiaomi',<br />       PROPERTY('device', 'amplitude_user') contains 'pad'<br />       ),<br />       'tablet',<br />      '(none)'<br />    )<br />  )<br />  )

The drawback to this solution is a) your org needs access to derived properties, and b) you need to investigate most common device family values used in your product when scoping the most reliable definition for your derived prop.

Also linking out this slack thread where trevin-bc’s org has instrumentation on Screen Height, Screen Width, and Device Orientation so he was able to build out a slightly more complex setup in derived properties as well.

dangrainger

Drawback c)….devices evolve (new models, new vendors, etc) so the definition in the derived property would also evolve, meaning customers would need to regularly re-check it. This is something that should be done vendor-side in the OOTB property.

Beth Saunders

This became available as an OOTB property a few months back!

Quick Links

Give your vote

playback video in 9:16 in guides on phones
It would be great to have the option of playing back video (and having the video preview) in a 9:16 (vertical) orientation so that an end user of a video in a guide didn't have to full-screen the video in order to have it play in the correct orientation. It would also be great to have support for Wistia as more and more…
Grouping reordering
Hi, I’d like to request a feature: it would be really helpful to have the ability to shuffle or reorder properties within an event, especially when grouping. Right now, adjusting the order of grouped outputs is quite cumbersome.
Fix the search when filtering
When changing a property value, because we often have complex and long values, we paste the exact value in the search bar. However the matching value will appear at the very top but all other values will remain, which makes the search complex and we lose a few seconds each time Here is a loom to show my point Thanks !!
Allow replacing the exposure flag key in dashboard templates
I am creating a template for our experiments dashboards I would like it to be as self serve as possible, making stakeholders changing the fewest things as possible. They have the ability to change the properties values but NOT the exposure key, which is a problem as they have to go in every chart and change the key, which…

View All