You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can I suggest to add a bit more information about how to specify the deviceID?
Because it is not very clear for the customer that the deviceID is used for identifying each user that connects to the application.
And needs to be used with only digits.
Based on a conversation on Slack: Custom applications have the same behavior then mobile applications: Not every session is tagged, especially when the user did not accept the privacy settings. Therefore the metric is based on the device id.
It says "Replace with unique value per device/installation" and you say: "Because it is not very clear for the customer that the deviceID is used for identifying each user that connects to the application. And needs to be used with only digits."
So I believe the comment says already that this needs to be unique and for sure not the application Id.
We will discuss this with the documentation team as well, but what do you have on your mind? What is not clear upon the mobile documentation about the internal user id?
Hi Matthias, thank you for your feedbacks.
I just find "per device/installation" confusing. Just explaining how deviceID is used by Openkit should be enough!
Also, the documentation only describes the use of the user tag and the internal user id but nothing about the deviceID in the case of a custom app.
Can I suggest to add a bit more information about how to specify the deviceID?
Because it is not very clear for the customer that the deviceID is used for identifying each user that connects to the application.
And needs to be used with only digits.
Based on a conversation on Slack:
Custom applications have the same behavior then mobile applications: Not every session is tagged, especially when the user did not accept the privacy settings. Therefore the metric is based on the device id.
The official documentation is also not very clear: https://docs.dynatrace.com/docs/shortlink/user-session#user-session-identification
My customer has implemented it by specifying the ID of the application and not the ID of the users so in consequence, only 1 unique user was reported:
Thank you!
The text was updated successfully, but these errors were encountered: