macOS

Deploying the Web Insights Browser Extension on macOS

This guide explains how to deploy the Web Insights for WhatPulse browser extension to managed macOS devices. The extension can be force-installed to Chromium-based browsers (Google Chrome, Microsoft Edge, Brave) and Mozilla Firefox using MDM configuration profiles or a local policies.json file. Force-installed extensions are installed silently and cannot be removed or disabled by end users.

Prerequisites

• macOS devices enrolled in your MDM solution (e.g., Jamf Pro, Microsoft Intune, Kandji, Mosyle)
• Administrative access to your MDM console
• Target browsers installed on managed devices

Extension Identifiers

Use the following identifiers when configuring deployment policies:

Browser	Identifier	Value
Chrome / Edge / Chromium	Extension ID	fnfhoihlmikplapbgegdmpifhgmaigbf
Chrome / Edge / Chromium	Update URL	https://clients2.google.com/service/update2/crx
Firefox	Add-on ID	web-insights-for-whatpulse
Firefox	Install URL	https://addons.mozilla.org/firefox/downloads/latest/web-insights-for-whatpulse/latest.xpi

Deploying to Chromium-Based Browsers

Chromium-based browsers on macOS use the same policy keys as on Windows. The ExtensionInstallForcelist key is delivered via a managed preferences configuration profile instead of Group Policy.

The force-install value combines the extension ID and update URL, separated by a semicolon:

fnfhoihlmikplapbgegdmpifhgmaigbf;https://clients2.google.com/service/update2/crx

The configuration profile targets the following preference domains:

• Google Chrome: com.google.Chrome
• Microsoft Edge: com.microsoft.Edge

Example: Jamf Pro

1. Create a Configuration Profile: In Jamf Pro, go to Computers → Configuration Profiles → New. Name the profile (e.g., "Web Insights Extension - Chrome").

2. Add Custom Settings: Select Application & Custom Settings and click Configure. Set the Preference Domain to com.google.Chrome (or com.microsoft.Edge for Edge).

3. Add the Policy Payload: Upload or paste the following property list content:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>ExtensionInstallForcelist</key>
    <array>
        <string>fnfhoihlmikplapbgegdmpifhgmaigbf;https://clients2.google.com/service/update2/crx</string>
    </array>
</dict>
</plist>

4. Scope and Deploy: Assign the profile to the target device group and save. Devices will receive the profile at their next check-in and the extension will install on the next browser launch.

Example: Microsoft Intune (macOS)

1. Create a Configuration Profile: In the Intune admin center, go to Devices → macOS → Configuration profiles → Create profile. Select Settings catalog as the profile type.

2. Add the Extension Policy: Search for Google Chrome - Extensions (or Microsoft Edge - Extensions) and select ExtensionInstallForcelist.

3. Configure the Value: Add the force-install string:

fnfhoihlmikplapbgegdmpifhgmaigbf;https://clients2.google.com/service/update2/crx

4. Assign and Deploy: Assign the profile to the appropriate device group and save. Enrolled Macs will receive the policy at their next sync.

Deploying to Firefox

Firefox on macOS supports enterprise extension deployment via MDM configuration profiles or a local policies.json file.

Option 1: MDM Configuration Profile

Push a configuration profile targeting the org.mozilla.firefox preference domain with the extension install policy. The payload should contain:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Extensions</key>
    <dict>
        <key>Install</key>
        <array>
            <string>https://addons.mozilla.org/firefox/downloads/latest/web-insights-for-whatpulse/latest.xpi</string>
        </array>
    </dict>
</dict>
</plist>

Deploy this profile through your MDM solution (Jamf Pro, Intune, Kandji, etc.) to the target device group. Firefox will install the extension on the next launch.

Option 2: policies.json

For environments where MDM-based Firefox configuration is not available, deploy a policies.json file to the Firefox distribution directory:

/Applications/Firefox.app/Contents/Resources/distribution/policies.json

{
  "policies": {
    "Extensions": {
      "Install": [
        "https://addons.mozilla.org/firefox/downloads/latest/web-insights-for-whatpulse/latest.xpi"
      ]
    }
  }
}

You can deploy this file using a script pushed through your MDM or any other file distribution method. For example, using a Jamf Pro script:

#!/bin/bash
mkdir -p "/Applications/Firefox.app/Contents/Resources/distribution"
cat > "/Applications/Firefox.app/Contents/Resources/distribution/policies.json" << 'EOF'
{
  "policies": {
    "Extensions": {
      "Install": [
        "https://addons.mozilla.org/firefox/downloads/latest/web-insights-for-whatpulse/latest.xpi"
      ]
    }
  }
}
EOF

Firefox will install the extension on the next launch.

Verification

After deploying the extension, verify that it is installed and active:

1. Check the Browser: Open Chrome, Edge, or Firefox on a target Mac and navigate to the extensions page (chrome://extensions, edge://extensions, or about:addons). The Web Insights for WhatPulse extension should be listed as installed and enabled, with a note that it is managed by your organization.

2. Check the Toolbar: The Web Insights icon should appear in the browser toolbar.

3. Check WhatPulse Dashboard: Log in to your WhatPulse Professional dashboard. Devices with the extension installed and the WhatPulse desktop client running should begin reporting web application usage data.