macOS support for ControlUp for Apps is currently in Beta. To join the Beta program, contact your ControlUp representative.
-
The first time you open ControlUp for Apps, a setup wizard walks you through the deployment steps. Follow the instructions in the wizard or use this article to deploy ControlUp for Apps on macOS devices.
-
For Windows deployment instructions, see Deploy ControlUp for Apps.
ControlUp for Apps collects web application data from supported macOS devices using the following components:
- ControlUp for Apps module: An add-on for the ControlUp for Desktops Agent that runs on the device.
- ControlUp for Apps browser extension: Required for capturing web application usage and experience metrics from supported browsers.
macOS deployment depends on how your Mac devices are managed. Use the unmanaged deployment path only for Mac devices that are not managed by Mobile Device Management (MDM). If the device is managed by an MDM solution, use the MDM-managed deployment path.
Prerequisites
Read ControlUp for Apps Overview for general prerequisites.
For macOS deployment, make sure that:
- The macOS device has ControlUp for Desktops Agent version 2.18 or higher installed.
- The macOS device can receive the supported ControlUp for Apps module version available for your tenant.
- Employees access monitored applications with Google Chrome or Microsoft Edge.
- For unmanaged Mac devices, the device can access the official Chrome and Edge web stores.
- For MDM-managed Mac devices, you can deploy browser extension configuration profiles through your MDM tool, such as Jamf, Microsoft Intune, or Kandji.
Deployment Instructions
To access deployment settings, go to Settings > Applications.

Deploy the ControlUp for Apps Module
- Select the Deployment tab.
- Add or edit a deployment rule.
- Set Platform to macOS.
- In Version, select the supported macOS version available for your tenant.
- Select the target device groups or device tags. To learn how to create and manage them, see Organize Devices with Groups and Tags.
- Click Apply.
The selected version is installed on macOS devices that match the selected device groups or device tags.
Deploy the Browser Extension
Browser extension deployment for macOS depends on how your Mac devices are managed:
- Unmanaged Mac Devices: Use this method only for Mac devices that are not managed by Mobile Device Management (MDM).
- MDM-Managed Mac Devices: Use your MDM tool to deploy the browser extension.
Browser extension deployment rules currently don't include a platform setting. If your Windows and Mac devices use different browser extension deployment methods, use device groups or device tags to make sure the installation rules target the correct devices. Place more specific rules above broader rules.
For example, if Windows devices install the extension from the ControlUp CDN and Mac devices are managed through MDM, use a device group or tag to target the CDN rule only to the Windows devices.
The ControlUp CDN is not currently supported for macOS. If a Mac device matches an extension deployment rule set to Automatically install via CDN, the extension is not installed.
Unmanaged Mac Devices
- Select the Extensions tab.
- Add or edit an extension deployment rule.
- Set Browser extension deployment to Automatically install via Web Store.
- Select the target device groups or device tags.
- Under Targeted browsers, select Google Chrome, Microsoft Edge, or both.
- Click Save changes.
- Ask users to log off and log back in for the extension to become operational.
ControlUp deploys the browser extension from the official Chrome and Edge web stores.
MDM-Managed Mac Devices
- Select the Extensions tab.
- Review your extension deployment rules and make sure the MDM-managed Mac devices don't match a rule set to Automatically install via CDN or Automatically install via Web Store.
- If necessary, use device groups or device tags to limit those installation rules to the devices where ControlUp should install the extension.
- If you changed an extension deployment rule, click Save changes.
- Deploy the required browser extension configuration profiles through your MDM tool.
- Ask users to log off and log back in after the ControlUp for Apps module and browser extension configuration are deployed.
If you use an extension deployment rule specifically for your MDM-managed Mac devices, set Browser extension deployment to Do not install.
Setting Browser extension deployment to Do not install prevents ControlUp from installing the browser extension on those devices.
The MDM configuration profiles force-install the ControlUp for Apps browser extension from the official browser web stores. Dynamic runtime settings are handled by the ControlUp for Apps module on the device.
Post-Deployment Verification
After users log back in, verify that the browser extension is communicating with the local ControlUp for Apps module.
Open the extension UI from the browser. Online indicates that the browser extension is connected to the local module.
![]()
After employees access monitored App Groups from Google Chrome or Microsoft Edge, macOS data appears in ControlUp for Apps.
Troubleshooting
If macOS data does not appear in ControlUp for Apps, check the following:
-
Module deployment
- The device matches the macOS deployment rule.
- The ControlUp for Apps module is installed.
-
Browser extension deployment
- For unmanaged Mac devices:
- The device matches an extension deployment rule set to Automatically install via Web Store.
- The device does not match a rule set to Automatically install via CDN.
- Google Chrome or Microsoft Edge is included under Targeted browsers.
- For MDM-managed Mac devices:
- The device does not match a rule set to Automatically install via CDN or Automatically install via Web Store.
- The extension is deployed through your MDM tool.
- For unmanaged Mac devices:
-
Connection
- The user logged off and logged back in after deployment.
- The browser extension UI shows Online.
Enable Logs for Troubleshooting
If you encounter deployment issues or communication errors, ControlUp Support might ask you to enable diagnostic logs.
- Go to Settings > Applications.
- Select the Advanced tab.
- Under Save logs, select Yes.
After logging is enabled, diagnostic logs are saved locally on the macOS device in the following folder:
/usr/local/com.controlup.edgedx.agent/Modules/appdx/logs
Copy the log files from this folder and provide them to ControlUp Support upon request.
MDM Policy Verification
For MDM-managed Mac devices, verify in your MDM tool that the browser extension configuration profile was deployed to the target devices.
You can also verify that the browser received the extension policy:
- In Google Chrome, open
chrome://policy. - In Microsoft Edge, open
edge://policy.
If the extension is installed but does not communicate with the local module, contact ControlUp Support.