Monetate User Roles

Individual user roles give you the ability to limit what members of your organization can do in Monetate. This acts as a failsafe to help prevent against inadvertent mistakes and malicious changes to your site.

Monetate provides you with five different user roles, and you should add checks and balances to your process to help alleviate mistakes or launching experiences that aren't complete. Before you assign a user role, you must understand what changes you can make to your site with Monetate and what each user role can do. See Manage Users for more information.

Consider the size of your team and business needs before assigning anyone a role. It is always better to err on the side of matching level to access with jobs people need to execute. You can manage changes to user roles at any time. These considerations are equally important when you work with a partner outside of your organization to fulfill certain roles within your Monetate account.

Once you have a good understanding of the user roles that Monetate offers, you may want to consider the following guidelines for assigning them to your team:

  • Reporting Only: Appropriate for anyone in an analytics or data analysis role
  • Experience Building: Appropriate for anyone in a marketer or marketing analyst role
  • Experience Building with Activation: Appropriate for anyone in a supervisory role or someone higher in your organization who is responsible for marketing efforts
  • Action Building: Appropriate for anyone in a marketer, IT, or developer role
  • Administrator: Appropriate for the person who owns the Monetate account at your organization

You may want to avoid assigning the same person who builds actions in Monetate with the ability to also activate experiences. This gives you an extra opportunity to test an experience before it goes live to your customers. If you want to fine tune permissions on certain accounts, submit a support ticket using the Kibo Technical Support portal (

The example below provides a basic workflow that you can use to manage roles for your team.

  • Bob (Web developer, Action Building role): Bob creates all the action assets to are used on the site. Today, he created an HTML action that inserts information about a sale below the navigation.
  • Alice (marketer, Experience Building role): Alice uses Bob's action assets and sets up the WHO, WHAT, WHEN, and WHY for an experience that creates a personalized experience for site visitors.
  • Shauna (QA, Experience Building with Activation role): Shauna receives a ticket to review Alice's experience that is scheduled to go live in a few days. Shauna tests this experience to see how it looks in all the latest browsers. When everything looks as expected, Shauna activates the experience.

It's possible to use Monetate without assigning anyone at your organization an Administrator role. This prevents anyone from maliciously or accidentally adding or deleting users but requires you to contact your account manager when you need to make these type of changes.