Description for sources
Thora Gudfinnsdottir
Teams use Avo sources to represent specific codebases or application contexts, but there’s currently no way to document what a source actually represents. This makes “source-aware” data design hard to scale and relies on tribal knowledge.
Request
Add a description field to sources in the Source Management view and surface that description where sources are used, such as:
- Event details (via tooltip or info icon)
- Source details
- Journey triggers
Why this matters
Clear source descriptions help editors and reviewers understand which app or codebase they’re working in, improving consistency and reducing confusion in multi-platform tracking plans.