Skip to main content
If event logs are not visible after distributing the extension, follow the steps below to retrieve Diag data.

​
Steps to Retrieve Diag Data

The following steps describe how to retrieve Diag data from the extension icon in Chrome.
For Chrome or Edge, open the following HTML page directly and follow step 3 onward in these steps.Chrome: chrome-extension://bdeanmdeckegmfjpbnngomallcedjold/options.htmlEdge (latest): chrome-extension://flggmhlpipcopffjfkpgkoljghfkmfcg/options.html
  1. Click the extension icon in the upper-right corner of your browser. Extension icon in the upper-right corner of the browser
  2. Click the gear icon in the upper-right corner of the extension screen. Gear icon in the upper-right corner of the extension screen
  3. Click Diagnostic Data in the lower-right corner of the extension. Diagnostic Data button
  4. Click OK, then paste the copied data into a text editor and save it. OK dialog

​
How to Interpret Diag Data

Reviewing Diag data lets you quickly determine whether data is being sent correctly. It also helps you identify where a configuration issue may exist.
  1. Check the four required fields All four of the following fields must be present for data to be sent successfully. If any are missing, proceed to step 2 and beyond.
    FieldDescriptionWhat to check
    EmailEmail address of the target userConfirm the value is not null.
    apiKeyAuthentication keyConfirm a valid string is present.
    OrganizationIDOrganization IDConfirm organizationId is not null.
    isActiveConnection statusConfirm the value is "isActive": true.
  2. Required parameter details (Email priority order) The email property displays the email address currently in use, based on the following priority. If an unexpected address appears, check whether a value exists in the higher-priority fields.
    1. manualEmail: Manually entered (highest priority)
    2. managedEmail: Retrieved from the OS or MDM (mobile device management)
    3. profileEmail: Retrieved from the browser login information
  3. If apiKey, OrganizationID, or CreatedDate are not visible Go to Settings > Organization > Browser Extension and copy the value from Extension Policy. Then set the value found within the extension policy.
  4. Verify the distribution status of the extension: Confirm that the extension is installed. Open the policy page in your browser (for example, chrome://policy) and verify that the settings have been applied. If no values appear in the policy, check the registry or configuration settings on the OS side. If they are also absent there, check the settings in the distribution source (such as MDM).
  5. Review the FAQ below and follow the steps on each help page, then recheck the values in the Diag data.
  6. If the issue persists after following the steps above, include the retrieved Diag data and contact the support desk.

​
FAQ

​
Q. What should I watch out for when configuring the registry?

A. The registry path differs between Chrome and Edge. (Reference: Register Parameters for the Extension in the Registry) If you configured the wrong path, remove the extension from the browser’s management console and reinstall it.
  • Chrome path: Software\Policies\Google\Chrome\3rdparty\extensions\bdeanmdeckegmfjpbnngomallcedjold\policy
  • Edge path: SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\flggmhlpipcopffjfkpgkoljghfkmfcg\policy

​
Q. Can I use a configuration profile without MDM?

A. This is not currently supported. Due to Chrome extension security restrictions, a manually created plist loads in the browser. However, the extension cannot read it.

​
Q. Do I need to set a different EMAIL for each user?

A. We recommend doing so. The extension sends the email address to the server as the identifier of the operator. In principle, any value in email address format works. For example, you can use the PC name as the local part (e.g., HOSTNAME@example.com). The sent email address appears on the web console as-is. However, it does not link to an actual user account. As a result, it may be difficult to use for data such as last-used dates. (It is sufficient for Shadow IT purposes.)
Last modified on July 13, 2026