Unit groups

Company > Units > Groups

Unit groups classify a Unit’s place in the company, such as sales district or territory, a line of business, geographical region, time zone, or managerial level. Users can filter and analyze survey data along these organizational lines, for example to find the month-over-month average scores for stores of a particular region.

For more information, see Unit groups and hierarchies and Units and unit groups.

Use this screen to:

  • Create and manage Unit groups.

  • Optionally edit Unit group data values, but doing so is not recommended. Instead, use the Auto Importer to load Unit Group data values when loading Unit (Org Hierarchy) data.

Properties

Name
Name of the Unit Group as it will appear in reporting. The Name can be changed, but the Identifier should not.
Identifier

Unique, case-sensitive identifier for each Unit Group. Unit Groups can be referenced in reporting and conditions by preceding the identifier with ug_, like this: ug_Identifier.

Do not change the Identifier value after data for the Unit Group is collected. Importers, report filters, and other configurations might reference the Identifier. Changing its value can cause errors elsewhere in Experience Cloud if those referencing configurations are not also changed. 

Tip: When building a program it is important to have a consistent naming convention for creating identifiers.

Medallia convention is identifiers should match the nesting in the Groups editor list, separated by underscores. For example, "location_district" is a Unit Group named District in a container group named Location.

Description

Internal comments about the group, such as a description of the group and a statement of the intended use.

When manually managing groups (not recommended) it is best practice to include the date the group was added or updated, who added or changed the group.

Include in extended benchmark

Turn on to allow extending benchmarking of this group.

This property is used in conjunction with the Extended Benchmarking or Extended Benchmarking if access >= 1 unit in Capabilities. A user or role with one of these capabilities can benchmark against any Unit group that has this box option turned on, as long as the user has access to at least one Unit in that Unit group. For example, a user who can view hotel scores for a hotel in Chicago (Unit) can benchmark against aggregate scores for Illinois (Unit Group).

Unit Group Data Fields
The remainder of the properties are the company-specific Unit groups data fields.
Important: Medallia best practice is to NOT define Unit Group Data fields because their values cannot be loaded with the Auto Importer. Consider using Unit data fields instead.
Units (properties)
Informational list of Units that are members of this group.

Tips and best practices

  • Never use the the Unit Group editor to delete a group from a live company. Doing so might corrupt the company structure in a way that cannot be saved. 

  • When you are building a new hierarchy, first create the groups and organize how they appear. Later, add in all the child values through Auto Importer.

  • The first level of groups under the All Units should be a unit-type to allow easy scaling of the program. Do this even if the company (currently) has only one unit type.  

  • Do not edit Unit group data values in the Groups or Groups Admin editors. The values may change the next time Units are loaded from the company, and doing so causes future new values to not appear alphabetically in the group.