Glossary

The glossary aligns the language your organization uses across platforms, so that when someone asks about “ROAS” or “spend”, Adverity Atlas maps it to the right columns and the right arithmetic, not a plausible guess. It is the single biggest lever on answer accuracy.

What a concept is

Each entry is a concept: a business term with the metadata Adverity Atlas needs to use it correctly. Concepts come in five categories:

• Metric: A measurable value, often computed, ROAS, CPA, spend

• Dimension: A categorical attribute to group or filter by, channel, campaign, country

• Identifier: A key that identifies a thing, campaign ID, account ID

• Timestamp: A point in time, so the reporting grain is recorded rather than guessed, report date, load timestamp

• Text / Label: Free text that is neither a measure nor something you group by, ad headline, notes

A concept carries more than a definition: synonyms, a calculation expression, how it aggregates, its output format (currency, percentage), and warnings about misuse. See Adding concepts for the full set.

Three tiers

The same term can be defined at three scopes. The most specific one wins:

1. Standard (global): A standard set of marketing concepts maintained by Adverity

2. Organization (tenant-wide): Your company’s shared vocabulary, across every workspace

3. Workspace: Local definitions, for when a team uses a term differently

Resolution runs workspace → organization → standard. A workspace concept overrides an organization one, which overrides the standard, see Concept layers.

Note

You do not edit standard concepts in place. Changing one creates an override at your tier and leaves the shared definition untouched, so the original is always intact. See Overrides.

How the glossary reaches Chat

When you ask a question, Adverity Atlas resolves the terms in it against the glossary before writing SQL, pulling the calculation, the aggregation rule, and the synonyms. A well-maintained glossary means fewer clarifying questions and answers that match how your team actually defines things.

Synonyms matter here: a concept’s aliases (say spend, cost, investment) all resolve to the same definition, so the question can use whichever word is natural.

From definition to calculation

A concept is portable: it says what “spend” means without saying which column holds it. The executable half is a measure, the aggregate SQL that computes the concept on one specific table. Concepts that have measures can be queried by name rather than reconstructed from raw columns each time. See Measures.

Finding a concept

The glossary list has a search box, Search concepts…, and four filters beside it. Search matches a concept’s name, its display name, its aliases, and its definition, so a term looked up by an alternative name still finds the right entry: searching CLTV reaches the concept whose primary name is customer_lifetime_value.

Filter	What it narrows to	Values
Scope	Which tier the winning definition came from	All Scopes, Standard, Organization, Workspace
Status	Where the concept is in its lifecycle	All Statuses, Draft, Active, Deprecated
Category	The kind of concept	All Categories, and the five categories above
Vertical	The industry a concept belongs to	All Verticals, and twelve industry verticals from accounting to sales

A sort select sits next to the filters: Name (A-Z), Name (Z-A), Recently Updated, Status, or Category.

The list holds only the concepts Chat can use in the current workspace: concepts someone created by hand, and concepts with visible data in the workspace. A term you expect but cannot find usually has no classified column or measure on a data source bound to this workspace. See Concept layers.

Filters carry into bulk actions, so narrowing the list first is the quickest way to act on a set of concepts, see Adding concepts.

Permissions

Roles are cumulative, so the role named is the lowest one that can take the action.

Action	Required role
Browse and search concepts	Viewer
Propose a term or an edit for approval	Analyst
Add and edit workspace concepts directly	Editor
Override a standard or organization concept	Editor
Approve a proposed term, manage the organization glossary	Knowledge Manager
Delete concepts	Admin

Two routes write to the glossary, and which one you get depends on your role. An Editor writes directly. An Analyst files the same change as a proposal, which a Knowledge Manager approves before it is written, see Adding concepts.

Promoting a workspace concept to the organization tier files an approval request rather than taking effect immediately, so shared vocabulary stays reviewed.

What’s next?

• Concept layers, the three tiers and how precedence resolves

• Adding concepts, every field on a concept and what it does

• Overrides, change a shared concept without touching the original

• Measures, the executable implementation of a concept on a table

• Knowledge, broader context that does not fit a single term

Was this page helpful? Yes No