Configure on Edge for Windows using Microsoft Intune – Pendo Help Center

This article covers the process to configure the Pendo Launcher extension on the Microsoft Edge web browser on a Windows computer using Microsoft Intune, which involves:

Determining values to configure.
Creating a PowerShell script.
Pushing the PowerShell scripts to your end-user devices.
Validating that the configuration was successful.

The process described in this article can be used to configure the following types of data:

API Key
Visitor ID
Metadata

Prerequisites

Before configuring the extension on end-user devices, you must first install it on end-user browsers. See the IT guide to deploying the Pendo Launcher for all implementation options. We also recommend reading the Plan your browser extension implementation article before running any deployment steps.

Step 1. Determine values to configure

To fully deploy the Pendo Launcher, you must configure an API key and Visitor ID. You can also include metadata, such as role or location, which can be used to enhance your analytics and guide targeting. For more information about selecting appropriate Visitor IDs and metadata, see Plan your browser extension implementation.

API key

Find the API key needed for Step 2 of the configuration process by navigating to Settings > Subscription Settings. Your unique extension API key is displayed at the top of the page and looks something like the following:

{
    "APIKey": {
        "Value": "c022bb1e-676d-4c58-731c-caf13fe12a89"
    }
}

Visitor ID and metadata

In most cases, Windows deployments provide only the Visitor ID through through the registry, which can be controlled by MDM tooling (such as Intune), and supplement metadata through other means, such as API or CSV upload. However, it's possible to provide metadata in the visitor object, if you have a method for dynamically retrieving the values on a user’s machine.

See Customize metadata sent to Pendo with Active Directory (AD) scripts for more information around providing metadata.

The visitor information should be formatted as a string JSON object with all PowerShell-incompatible characters escaped. See Microsoft’s documentation, About Quoting Rules, for information about PowerShell escape characters.

Step 2. Create a PowerShell script

Create a file on your own machine called pendo-launcher-config.ps1. Copy the following code into the file, then insert the API key value you determined in Step 1.

$api_key = "your-api-key-goes-here"
$username = $null

# Wait for username to be populated
while ($username -eq $null) {
    $username = (Get-CimInstance Win32_Process -Filter 'name = "explorer.exe"' | Invoke-CimMethod -MethodName getowner).User
    if ($username -is [array]) {
        $username = $username[0]
    }
    $username = $username -replace ' ', '.'
    Start-Sleep -Seconds 5 # Sleep for 5 seconds (optional)
}

# Define the Visitor ID by converting the username to an email address
# Your definition of a Visitor ID may vary

$visitor_id = $username + "@pendo.io"
$visitor_json = "{ `"id`": `"$visitor_id`" }"

$registry_path_edge = "HKLM:\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\lgpofjmgggolmabddgdmbgipcnblpnbm\policy"
$parent_path_edge = Split-Path -Path $registry_path_edge

# Create Edge policy path for the Pendo Launcher if it does not exist
if (!(Test-Path $parent_path_edge)) {
    New-Item-Path $parent_path_edge-Force -ItemType Directory | Out-Null
}

if (!(Test-Path $parent_path_edge\policy)) {
    New-Item-Path ("$parent_path_edge\policy") -Force -ItemType Directory | Out-Null
}

# Set the API Key, Visitor ID, and Data Environment policies
Set-ItemProperty -Path $registry_path_edge -Name "APIKey" -Value $api_key
Set-ItemProperty -Path $registry_path_edge -Name "visitor" -Value $visitor_json -Type ExpandString

# For eu environments, change io to eu; for US1 environments, change io to us1; for Japan environments, change io to jpn
Set-ItemProperty -Path $registry_path_edge -Name "dataEnvironment" -Value "io"

exit 0

Step 3. Push your PowerShell Script to end-user devices

For complete documentation from Microsoft, see: Use PowerShell scripts on Windows 10/11 devices in Intune.

Navigate to the Microsoft Intune Admin Center: https://intune.microsoft.com
Select Devices > Scripts from the left-side menu.
Select + Add at the top of the Scripts page. This adds a new script.
Select Windows 10 and later from the dropdown menu.
In the Basics tab, enter a descriptive name for your script, such as "Pendo Launcher Configuration". Select Next to continue.
In the Script settings tab, upload the pendo-launcher-config.ps1 file created in Step 2. Ensure that Run this script using the logged in credentials is set to No. Select Next to continue.
In the Assignments tab, select a group of devices to deploy the launcher configuration to. Select Next to continue.
- If you followed the steps in Install on Edge for Windows using Microsoft Intune, this should be the same group you targeted for the Pendo Launcher force install.
- We recommend testing and validating your deployment on a single device first and then gradually increasing the assignment scope until it covers the entire body of end-user devices.
In the Review + add tab, check your script, settings, and group assignments.
Select Add when you're done.

Step 4. Validate your configuration

First, test the script on a single device that you can physically access to verify correct configuration. Validation involves confirming the registry keys are set correctly and that the extension is configured as expected.

Confirm the presence of the registry key

On your Windows device, open the registry editor and enter "regedit" into the search box of the task bar and then select Registry Editor (Desktop app) from the results.
Navigate to the registry key location: HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Edge > 3rdparty > extensions > lgpofjmgggolmabddgdmbgipcnblpnbm

The registry keys should look similar to the following:

Confirm the extension is configured in the browser

After confirming that the registry keys are set, validate that the content if formatted correctly by checking that the browser extension is working. Intune can take up to 24 hours to run your configuration script on the end device.

Open Edge on a device that has the configuration profile present. If the app is already running, quit and reopen it.
In your browser, copy and paste the following into your address bar: edge://extensions
Find the Pendo Launcher extension in the top-right corner of your browser toolbar. If the extension isn't visible, you might need to view more extensions by selecting the puzzle icon.
Right-click on the extension icon and select Show Debug Info.
Select Show Configuration Tab > IT-Managed Config.
Check that the values match the values configured in your registry keys. If your dataEnvironment is set to the default value of io then the dataEnvironment key doesn't display in this view.