Where do I get the Device Type in the Data Feed | Community
Skip to main content
N
NicoleNL
Level 2
December 19, 2024
Solved

Where do I get the Device Type in the Data Feed

  • December 19, 2024
  • 2 replies
  • 15366 views
I am trying to find out how to identify the device type of a hit (Mobile Phone, Tablet, Set-top Box for example) in the Adobe Data Feed files.  I'm wondering if it can be obtained from the mobile_attributes.tsv file (we don't currently have this file, so I don't know what values each column contains).  Also, I read the documentation about the mobile attributes file, can someone explain why we cannot get the mobile_attributes.tsv file if we have the user_agent column included in the hit data feed?
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Harveer_SinghGi1

Hi @NicoleNL ,

For this information you need to get mobile_attributes.tsv lookup file which is not available by default in the lookups delivered with feed. To get this file you need to enable Dynamic lookups on your feed which can be requested through Adobe Customer Care and has some prerequisites,

  1. For mobile_attributes.tsv, you must include mobile_id in the feed
  2. The feed should not have user_agent, ch_hdr and ch_js columns

Adobe partners with DeviceAtlas to obtain device type from the collected user_agent. The data is proprietary to DeviceAtlas due to which Adobe cannot share the key (user_agent) and lookup data.
You can refer to this documentation for more such lookups available through dynamic lookup: https://experienceleague.adobe.com/en/docs/analytics/export/analytics-data-feed/data-feed-contents/dynamic-lookups

2 replies

Harveer_SinghGi1
Community Advisor
Harveer_SinghGi1Community AdvisorAccepted solution
Community Advisor
December 19, 2024

Hi @NicoleNL ,

For this information you need to get mobile_attributes.tsv lookup file which is not available by default in the lookups delivered with feed. To get this file you need to enable Dynamic lookups on your feed which can be requested through Adobe Customer Care and has some prerequisites,

  1. For mobile_attributes.tsv, you must include mobile_id in the feed
  2. The feed should not have user_agent, ch_hdr and ch_js columns

Adobe partners with DeviceAtlas to obtain device type from the collected user_agent. The data is proprietary to DeviceAtlas due to which Adobe cannot share the key (user_agent) and lookup data.
You can refer to this documentation for more such lookups available through dynamic lookup: https://experienceleague.adobe.com/en/docs/analytics/export/analytics-data-feed/data-feed-contents/dynamic-lookups

    N
    NicoleNLAuthor
    Level 2
    December 19, 2024

    We already get the carrier.tsv and operating_system_type.tsv dynamic lookup files but could not get mobile_attributes because we have user_agent in our hit_data data feed.  We will remove that first and then ask for the mobile_attributes file.  Sounds like it will be helpful for us.  Thanks for your help!

      Isha Gupta
      Community Advisor and Adobe Champion
      Isha GuptaCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      December 19, 2024

      Hey @nicolenl ,

       

      So, it looks like Adobe does not directly populate that information and that's why it's not available in Data feeds. As mentioned in this thread - 

       

      "Adobe Analytics takes the mobile_id column, pairs it with a backend lookup table provided by DeviceAtlas, then displays that value in reporting. Due to contractual obligations Adobe has with DeviceAtlas, that lookup table cannot be disclosed."

       

      Another related one for more info on this - https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/mobile-device-type-values-differences-adobe-analytics-vs-adobe/m-p/579165

       

      Hope this helps!

       

      Best,

      Isha

        N
        NicoleNLAuthor
        Level 2
        December 19, 2024

        Thanks @isha__gupta! 

          Terms & ConditionsAccessibility statement

          Loading footer...