Use Bloomreach Experience Manager

Bloomreach Experience Manager allows you to create content, customize the look and feel of your web pages, manage the channels through which you communicate your content, and monitor how site visitors interact with your content. Combined, these features help you create outstanding customer experiences. This walkthrough helps you get started on authoring and editing with Bloomreach Experience Manager. Since most day to day activities of content editors takes place in the Content application, this manual focuses on this application.

Log in to Bloomreach Experience Manager

Use the credentials provided on the login page to log in as author, editor or admin. Depending on your role, some or all of the icons below in the leftmost column of the CMS UI. Clicking on them brings you to the corresponding application: 


Shows your Todo-list, an overview recent activity, and allows password changes.

Experience manager

Helps you manage the various channels where content is published. You also see a preview of your (yet unpublished) changes.


In the Projects application, you can manage collections of changes made to channels.


The Content application is where you browse and manage your content.

Document search

The Document search application helps you manage content through a combination of powerful search functions and bulk actions on selections within the search result.

Insights > Content reports

The Content reports application (depending on the edition you are running) provides statistics about usage, pages most visited, broken links etc.

Audiences > Content audiences

The Content audiences application helps marketers target site visitors with custom site appearance and personalized content, based on characteristics of each individual visitor.

Setup > System

Allows administrators to manage  users, groups, permissions and system properties.


Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?