I am looking for confirmation that Adobe's Mobile Device Dimension is no longer able to identify the actual Android phone device used when a visitor views our website due in part to Google Chrome's User Agent Reduction Initiative? Note: Most of the Android devices are being aggregated under "Unknown Generic Android Mobile". Our query regarding this concern could not be answered by our Adobe Professional Consultant assigned to us.
Solved! Go to Solution.
Views
Replies
Total Likes
Hmmm I am not sure if that is the cause... I am seeing a lot of those devices in my data too, but when I break this down by Operating System, it seems to be predominantly Android 10? Meanwhile, I see new devices like Google Pixel 9 coming through in my data. I can also see a distribution of Browsers there too...
When I come at it from the other side, looking at Chrome 136.0, I can see this broken out to the generic and specific devices.
I haven't tried this yet, but if you aren't already, you could try enabling "Collect high entropy user-agent client hints" in your implementation? This is supposed to help with device reporting.
Hmmm I am not sure if that is the cause... I am seeing a lot of those devices in my data too, but when I break this down by Operating System, it seems to be predominantly Android 10? Meanwhile, I see new devices like Google Pixel 9 coming through in my data. I can also see a distribution of Browsers there too...
When I come at it from the other side, looking at Chrome 136.0, I can see this broken out to the generic and specific devices.
I haven't tried this yet, but if you aren't already, you could try enabling "Collect high entropy user-agent client hints" in your implementation? This is supposed to help with device reporting.
From what I understand, it’s partially tied to Chrome’s User-Agent Reduction initiative, which has been phasing out granular device details over time. That seems to impact what Adobe can pick up, especially for Android users coming through Chrome.
One thing worth checking is whether Client Hints are fully enabled in your implementation. Specifically, enabling high entropy UA client hints could help restore some of the lost detail, assuming your data collection setup supports it. Adobe does support this (I believe via the ECID library and AppMeasurement), but it’s not always turned on by default.
I would recommend confirming whether your tag setup is requesting those extra hints, it may not solve everything, but could give a more complete picture.
Hi @tkirwin,
Were you able to resolve this query with the help of the provided solutions, or do you still need further assistance? Please let us know. If any of the answers were helpful in moving you closer to a resolution, even partially, we encourage you to mark the one that helped the most as the 'Correct Reply.'
Thank you!
Views
Replies
Total Likes
Views
Likes
Replies