Dynamic placeholders in Web App webappURL config — how to use and enable

Android

When configuring an Esper Web App with a webappURL managed configuration key, you can embed dynamic placeholders such as ${esper.serialNumber} directly in the URL. Each device automatically substitutes its own identity values when the configuration is applied, giving every device a unique, device-specific URL without requiring separate configurations per device.

Why this happens

The Esper Agent resolves ${esper.*} placeholders locally on each device at the time the managed configuration is applied or re-converged. This means the substitution happens independently on every device using that device's own stored identity values, so no server-side templating or per-device configuration is needed.

Supported placeholders

Placeholder	Resolves to
`${esper.serialNumber}`	Device serial number
`${esper.uuid}`	Esper device UUID
`${esper.macAddress}`	Device MAC address
`${esper.deviceName}`	Esper device name

Configure the webappURL with dynamic placeholders

Open your Web App managed configuration in the Esper Console under Apps & Configuration → Managed Configurations and locate or create the configuration for your Web App.
Enter your URL with placeholders in the webappURL field using the supported placeholder syntax. For example:
```
{
  "webappURL": "https://example.com?serial=${esper.serialNumber}&deviceId=${esper.uuid}&mac=${esper.macAddress}&deviceName=${esper.deviceName}"
}
```
Use only the placeholder tokens listed above — unsupported tokens will not resolve and will appear literally in the URL.
Save and apply the configuration to your target devices or group. Navigate to Devices & Groups → [Device or Group Name] → Apps & Configuration and push the updated configuration. The Esper Agent will resolve the placeholders the next time the configuration converges on each device.

Verify: On a test device, confirm the Web App launches with a fully resolved URL — for example, https://example.com?serial=ABC123&deviceId=uuid-xyz&mac=00:11:22:33:44:55&deviceName=Tablet-01 — with no literal ${esper.*} tokens visible. Resolution typically completes within a few minutes of the configuration being applied. You can also check the Activity Feed on the device page to confirm the configuration was successfully applied.

Enable the Web App feature on your tenant

The Web App is a paid, opt-in feature that is not visible in the Esper Console by default. If you do not see the Web App option in your Console, follow these steps to get it enabled.

Check whether the Web App option is already available by navigating to Apps & Configuration in the Esper Console. If the Web App section is visible, the feature is already enabled on your tenant and no further action is needed.
Contact your Esper Account Manager if the Web App option is not visible. Reach out to discuss licensing and enablement for your tenant. Your Account Manager will confirm whether the feature is included in your current plan or requires an upgrade.
Wait for confirmation that enablement is complete. Once licensing is confirmed, Esper will enable the Web App feature on your tenant. This does not require any action on your part and does not affect existing device configurations.
Log out and log back into the Esper Console to refresh your session. Navigate to Apps & Configuration and confirm the Web App option is now visible before proceeding to create or deploy configurations.

Verify: After enablement, the Web App option should be visible in the Esper Console immediately after logging back in. If it is still not visible after a fresh login, proceed to the next section.

If this doesn't resolve it

If placeholders are not resolving on devices — meaning the literal token text such as ${esper.serialNumber} appears in the launched URL — or if the Web App feature remains unavailable after confirmed enablement, contact Esper Support with the following information:

The full managed configuration JSON you are using, including the webappURL value
The Esper device ID and serial number of an affected device
A screenshot or screen recording showing the unresolved URL in the Web App
The timestamp of the last configuration push, visible in the device's Activity Feed
Your tenant name and the name of your Account Manager if enablement is in progress

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.