# Better usage of the user agent data

**URL:** <https://forum.mautic.org/t/better-usage-of-the-user-agent-data/10270>\
**Category:** Ideas and Feature Requests\
**Created:** [February 25, 2018, 2:43pm UTC](https://forum.mautic.org/t/better-usage-of-the-user-agent-data/10270 "2018-02-25T14:43:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yannick038](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/yannick038/32/117_2.png) [@Yannick038](https://forum.mautic.org/u/Yannick038)\
**Post date:** [February 25, 2018, 2:43pm UTC](https://forum.mautic.org/t/better-usage-of-the-user-agent-data/10270/1 "2018-02-25T14:43:40Z")

</div>

Originally poste don github:  
[https://github.com/mautic/mautic/issues/4645](https://github.com/mautic/mautic/issues/4645)

don’t think this is a real FR maybe more an improvment

Current tracker only save and then display back user agent as a simple string  
For marketing users, this long string is complex to decrypt while we browse the timeline (on our last training we had questions about that : why while browsing with Chrome it is saved as Mozilla 5…

For each activity containing a user agent, should be real good to help the user to understand it

For example you can reading this webpage  
[http://www.whoishostingthis.com/tools/user-agent/#reading](http://www.whoishostingthis.com/tools/user-agent/#reading)

to know how to decrypt better the user agent

I know there’s no standard but implementing Chrome FF Safari Edge Opera ones would covers most of the use cases

---

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [October 17, 2019, 4:34pm UTC](https://forum.mautic.org/t/better-usage-of-the-user-agent-data/10270/2 "2019-10-17T16:34:08Z")

</div>

Closed on October 17, 2019, 4:34pm UTC


