Naming Conventions is only available for customers on the Business plan. To upgrade, contact your Customer Success Manager or email@example.com.
Naming Conventions lets Admins and Architects establish a consistent naming convention for new events. This allows you to keep your growing dataset organized by enforcing an accurate naming convention and makes it faster and easier for team members to find the exact event they need.
When the naming convention is active, team members creating shared events will have to follow the naming convention set up in their account. For example, if you set up a Location – Action – Object naming convention, then the event name field will be completed like this:
Set Up Naming Conventions
Before we jump in, here are a couple of important things to know about how naming conventions work:
- Naming conventions are applied per project: to apply the same naming convention across multiple projects, you will need to manually update this setting for each project.
- Naming conventions are not retroactive: events created prior to your naming convention being set up will need to be manually updated to match the naming convention. This also applies when the naming convention is updated; those updates will not be applied retroactively.
- Naming conventions will not apply when an event is being renamed: the structure is only enforced when an event is being named for the first time.
Admins and Architects can enable and disable the naming conventions feature by navigating to Account > Manage > Data Governance. Click the Set Up button to get started.
You’ll be prompted to configure the prefixes, which are the building blocks of your names, for your naming convention. The default (recommended) approach is to use a Location – Action convention.
When you click on the elements in the text field (in this case, Location or Action), you’ll be prompted to define a list of values for this prefix. Following our example, for the Location prefix, we may define website (our marketing site), app (in-app pages), and help center (our documentation hub) values for Location.
For Action, we’ll follow Heap’s event property types: view, click, submit, and change.
Click the + button to add an additional prefix. After the third prefix, you’ll be able to populate the rest of the event description when creating it.
To allow team members to enter unique values for any given prefix, we can update their role to grant them the ability to add new values. To grant team members the ability to add new values, navigate to Account > Manage > Roles, select the role you wish to provide these permissions for, and check the box next to Add New Values to Naming Conventions.
Once the new naming convention is set up, it will apply to all new events created via the Definitions page in this project. This allows you to establish different naming conventions for each of your projects. Review the next section to see what this looks like for team members.
Naming conventions cannot be applied to events retroactively to events that were created before the naming convention was set up.
Using Naming Conventions
After your naming convention has been set up, when team members are creating new shared events from the New Definitions drop-down on the Definitions page, they will only be able to use the defined naming convention. If permission has been granted, they can also add values to certain prefixes, such as the Object prefix below.
This naming convention will not apply to personal events, though users will see a prompt to structure their personal event like a shared event.
This naming convention will only apply to events created via the Events page. Events created via Live View and the Users View will not have this naming convention enforced. Support for the Event Visualizer is coming soon!