Configure Conductor's Live Editor
Note that this feature is currently part of a beta program. If you are interested in participating and you don't already have access, contact your Conductor Customer Success Manager or Account Manager.
This is an add-on feature in Conductor. To add it to your account, contact your Conductor Customer Success Manager or Account Manager.
Live Editor lets you make live changes to your website's pages directly from Conductor. To enable this, your organization must implement a JavaScript tag on your site. Once in place, this tag lets Conductor users edit and update elements on your website's pages using Conductor or from the Conductor for Google Chrome browser extension.
Please read through the following notes before implementing Live Editor:
- Many organizations might need to consult their internal IT teams to add this tag and to confirm whether this functionality abides by their organizations' change management policies.
- Implementation is performed at the web property-level. This means you will need unique tags for each web property in which you want to use Live Editor.
- You can control user access on a user-by-user basis for each web property you track in Conductor.
Live Editor uses a unique JavaScript tag (sometimes called a snippet or pixel), which load instructions for a page when someone opens it on their browser. Once this tag appears in your pages, you can add, remove, or replace content on a page from Conductor. Implementation of this tag is straightforward and can be done by an IT or web development team, or by a team member with direct access to your website’s tag manager or CMS.
Generate unique tag for your web property
Once Conductor has enabled Live Editor for the web property (a root domain or subdomain), you can generate the <script> tag your organization will need to add to that web property. The following examples are what this snippet looks like, depending on the tool you use for implementation:
If you use Google Tag Manager for implementation
(function() {var script = document.createElement('script');
script.type = 'text/javascript';
script.src = 'https://cdn-live.conductor.com/v1/9eb73df9-179b-464b-ab8e-33c9b2aeccf8/live.js';
script.setAttribute('integrity','sha123-123ABcdEFghHs2KGhZlUm6bBYv2MwbBJftYOHd1pQtlA00QXvCreBLb2qefKnXqK');
script.setAttribute('crossorigin','anonymous'); document.getElementsByTagName('head')[0].appendChild(script);
})();
</script>
If you use any other method for implementation
(These are NOT your tags—just an example of their appearance.)
Note that you will require a different tag for each web property you want to enable with Live Editor.
To generate these tags:
- Go to the Settings tab in Live Editor in Conductor or click Live in the side navigation and go to the Settings tab.
- Set up your web property for either of the following scenarios:
- If no tag has been generated in your account, click Set Up Live Editor.
- If a tag has already been generated in your account for a different web property, you can click Set Up Another Live Editor Tag.
- If no tag has been generated in your account, click Set Up Live Editor.
- In the field on the form, select the root domain or subdomain you want to generate a tag for.
- Click Generate. The newly-added web property and the <script> tag appear below.
With the tag generated, you can send them to the appropriate team to implement them as described below.
Add the tag to your web property
You can add the tag to your chosen web properties in one of two ways:
Tag Management System. If your organization uses a tag management system like Google Tag Manager or Tealium, you can add the unique tag to your tag management system. Be sure to add this tag inside the <head> section of the page.
Note for Google Tag Manager
Google Tag Manager requires a different format for its script. As a result, implementing the tag requires you to enter the Source and Integrity Key values from the generated tag and enter them in the relevant locations in the following Google Tag Manager script:
(function() { var script = document.createElement('script');
script.type = 'text/javascript'; script.src = '[SOURCE VALUE]';
script.setAttribute('integrity','[INTEGRITY KEY VALUE]'); script.setAttribute('crossorigin','anonymous');
document.getElementsByTagName('head')[0].appendChild(script);
})();
</script>
Where can you find these values in the generated tag? Here is an example tag with the values labeled:
Simply enter the values from your generated tag into the locations identified in the Google Tag Manager script. Then you can enter the finished tag into the <head> section of your Google Tag Manager.
HTML Template. You can also use an HTML template in your CMS to add the tag. Use a header template that your CMS uses for each page on the website so that the tag appears wherever you want to make changes with Live Editor.
Set User Permissions for Live Editor
Having the ability to update content on your site is a big responsibility. Conductor recognizes that you'll probably want strict control over who can and cannot use Live Editor. By default, users do not have access to Conductor's Live Editor feature.
Initially, your account will have a single user that can determine the level of access other users have to the feature. Unlike other user access settings in Conductor, Live Editor's access is determined on a user-by-user basis for each web property you integrate—completely separate from the permissions associated with Conductor user types.
Permission Configuration
Additionally, you can determine the scope of changes allowed by each Live Editor permission level. This means you can determine the areas of your site that a Admin or Publisher can make changes, as well as the types of changes they can make. By default, both Live Admins and Live Publishers may edit any page on the configured web property, and any of the page elements Live Editor allows you to change.
Note that to set user permissions for your integrated web properties, you must either:
- Be the initial user in your account designated to set user permissions for Live Editor.
- Have been given administrative permissions by another Live Editor administrator.
You can configure permission levels and assign Live Editor user permissions in the Live Editor activity. To get to Live Editor settings, go to the Settings tab in Live Editor in Conductor or click Live in the side navigation and go to the Settings tab.
Does your organization no longer have a Live Admin user to grant permission (for example, if your only Live Admin left your organization)? Contact your Conductor representative who can follow up with our Product and Engineering teams.
Configure Permission Levels
Live Editor has two permission levels you may customize: Live Admin and Live Publisher.
- Find the web property for which you want to configure permissions and click Edit Settings.
- In the form that appears, you can:
- Choose the areas of your site where Live Admins and Live Publishers may make edits. You can determine this by entering the specific URL paths that those users should have access to making changes:
- Choose the Page Elements to which Live Admins and Live Publishers may make edits.
- Choose the areas of your site where Live Admins and Live Publishers may make edits. You can determine this by entering the specific URL paths that those users should have access to making changes:
- Click Save.
Assign User Permissions
To configure which users may use Live Editor, and to determine which permission level they have:
- Find the web property for which you want to add Live Editor users and configure Live Editor permissions.
- Click Add another user and select the user from your account you want to configure with Live Editor permissions:
- Under the Access column, choose the Live Editor permission level you want the user to have. By default, this will be set to Live Publisher.
- Click Add.
Note that Conductor Admin users can also configure Live Editor permission levels in the User Settings activity:
- Follow the path Settings > User Management.
- Find the user in the table and click Manage.
- In the Live Editor Access section, choose the level of access—None, Publisher, or Admin—for each of the domains configured for your account.
- None is the default setting. Users have no access to Live Editor.
- Publisher lets the user access Live Editor, publish changes, but not edit Live Editor permissions for other users in your account.
- Admin lets the user access Live Editor, publish changes, and edit Live Editor permissions for other users in your account.