1. Pendo Adopt
  2. Installation
  3. Configure

Configure on Chrome for macOS using configuration profiles

Last updated:

This article covers the process to configure the Pendo Launcher extension on the Chrome web browser on a Mac computer using Mobile Device Management (MDM) tooling, which involves:

  1. Determining values to configure.
  2. Creating a .plist file on your own device.
  3. Pushing the .plist file to your end-user devices.
  4. 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 installation options. We also recommend reading the Plan your Adopt installation 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 Adopt installation.

API key

Find the API key needed for Step 2 of the configuration process by navigating to Settings > Subscription. 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

The visitor information should be formatted as a string JSON object with all XML incompatible characters escaped. To create this file:

1. Create a normal JSON object containing your information, such as:

{
  "id": "foo",
  "bar": "baz",
  "bingo": [
    1,
    2,
    3
  ],
  "tango": "2006-01-02T15:04:05.999-05:00"
}

2. Use an online tool to escape your text, such as freeformatter.com or codebeautify.org. The resulting text from the above object looks like:

{
  "id": "foo",
  "bar": "baz",
  "bingo": [
    1,
    2,
    3
  ],
  "tango": "2006-01-02T15:04:05.999-05:00"
}

3. Refer to your MDM tooling’s documentation for instructions on how to dynamically populate the values in this visitor object. For example, Jamf uses Payload Variables to dynamically insert values specific to the targeted end-user into configuration profiles.

Step 2. Create a .plist file

Create a file on your own machine called com.google.Chrome.extensions.epnhoepnmfjdbjjfanpjklemanhkjgil.plist. Copy the following code into the file, then insert the values you determined in Step 1.

<?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>APIKey</key>
    <string>YOUR API KEY HERE</string>
    <key>visitor</key>
    <string>YOUR VISITOR STRING HERE</string>
  </dict>
</plist>

Below is an example .plist file. 

<?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>APIKey</key>
    <string>c025bc1f-606d-4d62-731c-caf13fe12j24</string>
    <key>visitor</key>
    <string>{&quot;id&quot;: &quot;john.smith@example.com&quot;}</string>
  </dict>
</plist>

Step 3. Push your .plist file to end-user devices

Using your MDM tooling, push your .plist file as a configuration profile to end-user devices. The preference domain for this configuration profile is com.google.Chrome.extensions.epnhoepnmfjdbjjfanpjklemanhkjgil.plist. If your tooling requires the .plist file to be converted to a configuration profile before uploading, you can use the open source tool, mcxToProfile.

Your MDM tooling has specific instructions on how to deploy a custom configuration profile. Below is a list of documentation for some of the most common MDM tools used for Mac devices:

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 presence of the configuration profile and validating the correct browser behaviour.

Confirm the presence of the configuration profile

There are two ways to confirm a configuration profile is successfully configured:

Apple system settings

  1. On your Mac, choose System Settings in your Apple menu. 
  2. Select Privacy and Security in the sidebar.
  3. Select Profiles. You might need to scroll down to find it.
  4. Search for your configuration profile, which is the name configured in your MDM tool, to check that it's present.

The command line

  1. Open the Mac terminal app.
  2. Enter the command cd /Library/Managed\ Preferences to navigate to the managed preferences folder.
  3. Verify that the com.google.Chrome.plist file is present.
  4. Enter the command defaults read /Library/Managed\ Preferences/com.google.Chrome.
  5. Verify the contents match the values that you configured in Step 2.

Validate the browser behavior

Confirm that the browser is correctly reading the contents of the configuration profile.

  1. Open Chrome on the device with the configuration profile. If the Chrome app is already running, quit and re-open it.
  2. Install the Pendo Launcher browser extension on your Chrome browser. If you've already configured force-installation of the Pendo Launcher, you can skip this step.
  3. Visit any non-Chrome webpage, such as, https://pendo.io/. 
  4. Right-click on the Pendo Launcher extension icon in the top-right corner of your browser toolbar.
  5. Select Show Debug Info.
  6. Confirm that the Visitor ID in the Identified as field is correct.
  7. Select Show Configuration Info.
  8. Open the IT-Managed Config dropdown menu and search for your configuration values to check that they're present.

IT-Managed

Related articles