Application: Nomid MDM
Document: V1.0.0
Last updated: 02/07/2026
Editorial owner: Nomid MDM Documentation
Last editorial review: 02/07/2026
Editorial language: en-US
Nomid MDM allows administrators to use dynamic variables in Managed Configurations of Android applications.
These variables are automatically replaced with the actual device value when the policy is applied.
| Variable | Description | Example substitution |
|---|---|---|
%imei% |
Device IMEI | 357842105887001 |
%serial_number% |
Device serial number | R9ZT12345AB |
%serialnumber% |
Alias for %serial_number% (same behavior) |
R9ZT12345AB |
username, device_id, user_identifier).Example 1 – Automatic login using IMEI
username = %imei%
→ The app will receive: 357842105887001
Example 2 – Unique identifier using serial number
user_identifier = %serial_number%
→ The app will receive: R9ZT12345AB
Example 3 – Building strings with variables
account = user_%serialnumber%@company.com
→ The app will receive: user_R9ZT12345AB@company.com
⚠️ The minimum reapplication interval is 15 minutes.
If disabled, substitution occurs only when the user interacts with the Nomid launcher.
Current behavior:
Nomid MDM does not monitor new app installations on the device.
This means that if an app is installed after the policy has been applied, it will not immediately receive dynamic variables.
How to resolve:
Variables must be written exactly as supported (%imei%, %serial_number%, %serialnumber%).
If the app field does not support Managed Configurations, the variables will have no effect.
Always test in a pilot device group before rolling out to production.