What evidence would help you build a glossary around distinctions that change decisions?
A glossary should resolve confusing distinctions, not collect every term in a field. Decide which definitions belong beside a practical guide. Research public misunderstandings that lead to different actions, keeping multiple legitimate meanings explicit rather than presenting one vendor's preferred terminology as universal language or filling the page with circular definitions that leave the original task no easier to complete.
Find glossary distinctions that change decisions in this guide, with contextual definitions, inclusion examples and explicit product-specific meanings where needed.Define the editorial decision
Define the guide's task and collect terms appearing in relevant public questions. Include examples where two words are confused or one word has several operational meanings. Exclude jargon unrelated to a reader decision. Record the context and consequence of each ambiguity, distinguishing a missing definition from a disagreement about how a product chooses to implement or label the concept within its own interface.
Map evidence to the reader task
For each candidate term, identify a concrete inclusion and exclusion example. A useful definition should help a reader classify a case. Keep source-specific meanings attributed, especially for words such as audience, snapshot or engagement. Do not imply that a badge or a familiar term guarantees the same data access, counting unit or privacy semantics across products that use the word differently in their public documentation.
Test the angle against counterexamples
Compare definitions against actual questions and counterexamples. Look for synonyms that can be linked rather than repeated as separate entries. If a definition requires a larger conceptual explanation, give it a clear destination instead of compressing away the distinction. Public usage can inform wording, but should not override a documented product contract or justify inventing a definition that makes an unsupported capability appear standard or expected.
Prepare the bounded content brief
Deliver a short glossary brief with the decision each term clarifies, examples and authoritative references. If a term does not change understanding or action, omit it. Keep drafting and publication with the owner. Do not claim the glossary has been comprehension-tested, and avoid using definitions as a back door for unsubstantiated comparisons, universal coverage promises or a false impression that every community agrees on one meaning.
Keep the boundaries clear.
- For content glossary, a proposed example is not an observed product result.
- Badges indicate context for content glossary, not guaranteed access or audience coverage.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.