This guide provides a strategy for naming and organizational best practices to create consistency within your EventStream and AudienceStream account.
In this article:
As you build out your EventStream and AudienceStream configuration, you will have dozens, if not hundreds, of components to work with. Having a robust and consistent naming convention provides organization and clarity, enabling you to find attributes, audiences and other items quickly and confidently.
Some of the benefits include:
In most cases there should be a simple name that describes an attribute or audience e.g., Order Total or First Time Buyers. However, there may be important information about a component that requires a more specific name. Below is the recommended approach for naming.
Brand - Source - Descriptor - Specifier
"Order Total – Lifetime"
"Product Categories Viewed – Visitor (favorite)"
"Teal – OFL – Order Total – 30 Day"
"AS – ONL – Product Categories Viewed - Visit"
Start with the descriptor and specifier, then add on from there when necessary:
Prefixes are a way to help group similar items in the drop-down menus and selection lists throughout the UI. By using the same prefix in the name of several related omponents, all variations will appear in a group, making it clearer to see your options.
For example, you might have a visitor attribute indicating the "status" of the user, with a separate attribute for each status.
Using these names (without a prefix), the attributes will not appear together in the UI and you lose context about all possible statuses.
By using a consistent prefix, these attributes will be grouped together in the UI whenever a selection can be made, making it easier to see all options that are available:
We recommend that you create a labeling strategy suited to your account and organization. Examples of helpful labels can include:
The most important part of labeling is consistency--be sure to label all components associated to a label