Asset Labels

Asset labels allow marketers to label and group their assets in a logical way which allows them to generate better insights across multiple campaigns and periods of time. Labels can be added to Lists, Custom Events, Segments in lists, Content, Journeys, Cadence plans, Content Blocks and Data exchange assets (such as imports, tasks, data syncs, etc.) and can be used in generic exports and Reporting in Engage.

Asset labels are managed from the Admin Configuration and are subject to permissions: Read only and Access.

Read-only — User can see all the defined labels in the Admin configuration without the right to make any changes. They can always assign labels to assets.
Access — User can view, create, delete, merge and edit labels and assign these labels to assets. New labels can be created directly from the Admin Configuration tool as well as on the fly, from the Label field in an asset.

When none of the above permissions are given to the user, they will still be able to assign labels to assets.

Because these labels are managed labels and not free text like tags, they can be used for more structured reporting as well as for segmentation.

Note: Asset labels replace the legacy Tags feature and all existing Tags are migrated to Labels.

For every label it is possible to define one parent label. For example, the parent label 'Sales' is assigned to the label 'Summer Sales'. This is especially interesting for segmentation. Although there is a hierarchical structure upon defining a parent label, this is not reflected in the list of labels and the user can freely choose and assign any of the labels available in the drop-down list.

When labels are used in assets that are shared or duplicated with other organizations, several scenarios can occur:

The asset labels are already present in the targeted organization. In this case, all labels assigned to the shared/copied asset remain.
The asset labels are not yet present in the targeted organization and the user sharing/copying the asset has the necessary permissions in the targeted organization to create labels. In this case, the labels are added to the targeted organization and remain present in the shared/copied asset.
The asset labels are not yet present in the targeted organization and the user sharing/copying the asset does not have the necessary permissions in the targeted organization to create labels. In this case, the labels cannot be created in the targeted organization and the labels will not be visible in the shared/copied asset.