2026 Conductor Monitoring Upgrade Guide

Conductor is upgrading its Monitoring product to deliver it more natively in the entire Conductor platform.

What does this change mean for Conductor Monitoring Users?

The way you use Conductor Monitoring will stay exactly the same, but there are some administrative tasks you or someone at your organization will need to perform.

Jump to a task:

Bookmarks

The URL for Conductor Monitoring is changing from our legacy app.contentkingapp.com domain to app.cm.conductor.com. This means you will want to update any bookmarks you have to refer to this new domain.

Task 1: Update your bookmarks

Replace the app.contentkingapp.com domain with app.cm.conductor.com

 

Note!

If you access Conductor Monitoring through SSO from Conductor Intelligence, you won't need to make changes to your bookmarks. You'll continue accessing Conductor Monitoring from Conductor Intell

 

API connections

If your organization uses any of Conductor Monitoring's APIs, you'll need to update the base URL from https://api.contenkingapp.com to the new base URL https://api.cm.conductor.com.

Task 2: Update your API connections

Work with your developers to update the base URLs in your existing API connections.

You'll need to replace https://api.contentkingapp.com with https://api.cm.conductor.com

 

User Agent String

Depending on the user agent string you have configured for Conductor Monitoring, you'll need to take one or more of the following actions:

If your organization uses the the ContentKing user agent string in your monitoring settings, you will need to update it to the new Conductor option. If you use any other user agent, you'll need to enable an updated user agent string for it.

Task 3: Update your user agent

If you use ContentKing as your user agent

  1. In Conductor Monitoring, go to Settings.
  2. Click Monitoring.
  3. In the Settings section of this this tab, check to see what User Agent field is set to.
    • If it's anything other than ContentKing, skip to the next section in this task.
    • If it is ContentKing, click Edit.
  4. From the User Agent menu, select Conductor.
  5. Click Save.

If you use any user agent other than ContentKing

  1. In Conductor Monitoring, go to Settings.
  2. Click Monitoring.
  3. In the Settings section of this this tab, click Edit.
  4. At the top, click to enable the Enable new crawler identity toggle.
  5. Click Save.
 

Additionally, if your organization has previously whitelisted the ContentKing user agent string in your CDN settings, you will need to also whitelist the new Conductor user agent string.

Task 4: Whitelist the New User Agent String (if Necessary)

Work with your organization's web dev team (or whichever team owns your CDN) to confirm that—if you use user agent string to whitelist Conductor Monitoring's crawler—you update the string that appears under the option you have selected in the User Agent menu.

(This string should look identical to the previously whitelisted string except that (+https://whatis.contentkingapp.com) has been replaced by (+https://whatis.conductor.com).

Note

If your organization uses IP address to whitelist Conductor's crawler, no action is necessary to whitelist the new user agent. The new user agent uses the same IP addresses.