Device
Device
Status:
type: device
Description: The device on which the process represented by this resource is running.
This entity definition contains attributes without a role. Stable Entities MUST NOT have attributes without a defined role.
Attributes:
| Role | Key | Stability | Requirement Level | Value Type | Description | Example Values |
|---|---|---|---|---|---|---|
| Other | device.manufacturer |  | Recommended | string | The name of the device manufacturer [1] | Apple; Samsung |
| Other | device.model.identifier | | Recommended | string | The model identifier for the device [2] | iPhone3,4; SM-G920F |
| Other | device.model.name | | Recommended | string | The marketing name for the device model [3] | iPhone 6s Plus; Samsung Galaxy S6 |
| Other | device.id | | Opt-In | string | A unique identifier representing the device [4] | 123456789012345; 01:23:45:67:89:AB |
[1] device.manufacturer: The Android OS provides this field via Build. iOS apps SHOULD hardcode the value Apple.
[2] device.model.identifier: It’s recommended this value represents a machine-readable version of the model identifier rather than the market or consumer-friendly name of the device.
[3] device.model.name: It’s recommended this value represents a human-readable version of the device model rather than a machine-readable alternative.
[4] device.id: Its value SHOULD be identical for all apps on a device and it SHOULD NOT change if an app is uninstalled and re-installed.
However, it might be resettable by the user for all apps on a device.
Hardware IDs (e.g. vendor-specific serial number, IMEI or MAC address) MAY be used as values.
More information about Android identifier best practices can be found in the Android user data IDs guide.
This attribute may contain sensitive (PII) information. Caution should be taken when storing personal data or anything which can identify a user. GDPR and data protection laws may apply, ensure you do your own due diligence.
Due to these reasons, this identifier is not recommended for consumer applications and will likely result in rejection from both Google Play and App Store. However, it may be appropriate for specific enterprise scenarios, such as kiosk devices or enterprise-managed devices, with appropriate compliance clearance. Any instrumentation providing this identifier MUST implement it as an opt-in feature.
See app.installation.id for a more privacy-preserving alternative.
Feedback
Was this page helpful?
Thank you. Your feedback is appreciated!
Please let us know how we can improve this page. Your feedback is appreciated!