Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Introduce description field for Rules and Data Elements in Launch


Level 7


Description -

Currently, we only have the name of a Data Element or Rule to describe them. Notes are helpful for changes to an item but are not immediately visible from both the list and detail screens.

Why is this feature important to you -

Because I like to know what a thing does without having to look into it first. Also because it helps communicate functionality to others.

How would you like the feature to work -

Have a description field next or below the name of a Rule or Data Element in the detail screen. If an item has a description, show a little i-icon on the overview page that, upon hovering over it, shows the description as an overlay (like a tooltip).

Current Behaviour -




Community Advisor


If you need a description to understand what your data element does or your rule does then you have failed to name them correctly.

You should name your Adobe Launch data elements, rules, events, conditiions and actions in a way that only looking at the name should give you the indication of what it does.


For the code it is the same concept you should write the code in a self-documenting manner.


Please consider setting coding standards and tagging standards


Once these standards are set up you will see that your tagging experience will greatly improve.




Level 7


Thank you for the suggestion @Alexis_Cazes_. Naming conventions are a good practice and self-documentation is a nice goal in theory, but both are simply insufficient in reality. Especially in big and diverse teams working with both old and new implementations, names are not enough. This is especially true in tag management, where not every user has or needs a background in development.

It's similar to programming: Naming a variable clearly is a good start but comments and things like JSDoc exist for a reason. Not every information can (or should) be communicated through naming alone. On top of that, since Data Elements are referenced by name, there is an immediate conflict between giving them short vs. descriptive names.

So while small implementations from single developers are free to never use this feature, it will bring a lot of value and clarity to a lot of customers.