Many Tealium products use a shared configuration environment. Those environments often grow in complexity as they are iterated upon by many 'generations' of users over a period of years.
It's essential to the long-term success of those configurations that each user contributes to documenting their changes and follows Tealium's best practices.
These practices include:
In those notes, focus on the WHY instead of the WHAT.
For example, when manually removing a cookie with a TiQ extension:
This is especially true for any odd configuration.
If, as an extreme example, you are leaving behind a tag that is deliberately switched off, but must not be activated or removed, explain WHY instead of cryptically writing "Don't activate or remove".
We shouldn't leave unused configuration behind. If a tag is outdated and no longer being used, it should be deleted. Alternatively, if we are disabling tags for any reason, we must note the deactivation date for reference and add why it's being deactivated so future users can make informed decisions.
Labels help newcomers orient themselves and more seasoned team members find their way around more quickly - it's a very good idea to use them. This becomes more and more important as the configurations grow larger.