The Context System
Aliveo AI’s Context System is how you teach the platform to read your data the way your business does. Context isn’t code—it’s plain-English instructions, definitions, and conventions—but it powers every chat, dashboard, and automation agent on the platform.
This guide walks through the three levels of context, how they cascade, and where to set each one.
The Three Levels
Context is layered, from broadest to narrowest:
| Level | Scope | Typical contents |
|---|---|---|
| Global Context | All your businesses and accounts | Company-wide vocabulary, KPI definitions, acronyms, brand voice |
| Org Context | A single line of business | LoB-specific KPIs, campaign-naming conventions, market hierarchies |
| Account Context | A single (or a small group of) ad accounts | Account-specific exclusions, attribution windows, market mappings |
Each level can stand on its own, and each level inherits from its parent.
A useful mental model: Global is the company glossary, Org is the playbook for one team, and Account is the post-it note on a specific ad account.
How Cascading Works
When Aliveo AI runs against a specific ad account, it reads an effective context built in this order:
- The Global Context.
- The Org Context for the active line of business, placed after the Global text.
- The Account Context for the account(s) involved, placed after the Org text.
A narrower level never deletes what its parent says—it adds to it. To change an inherited rule, state the new rule explicitly at the narrower level. To leave the parent’s text out completely, turn off the include toggle on that level’s page. The combined text is what Aliveo reads when planning, generating code, validating answers, or summarizing.
Cascading in practice
- Define “ROAS = revenue ÷ ad spend” at the Global level once—every account inherits it.
- At the Org level, write “For this business, ROAS uses gross profit instead of revenue.”
- At the Account level for one campaign type, exclude branded-search conversions from the numerator.
Each context page shows the inherited text in a read-only box above your own, so you can see what is inherited and what is added at that level.
Setting Global Context
Global Context applies to every business and every account you have.
- Open My Account → Global Context.
- In the Context editor, describe your rules in plain English. Useful starting points:
- Acronyms — e.g. “BOF means bottom-of-funnel; TOF means top-of-funnel.”
- KPIs and formulas — e.g. “Primary KPI is CAC, defined as ad spend ÷ new customers.”
- Tone — e.g. “Use full month names in narrative summaries; never abbreviate.”
- Click Save. The page shows who last saved it and when.
To point to a specific document or dataset, type @ followed by its name—see Knowledge Documents.
Global Context cascades down—Org and Account context both inherit it.
Setting Org Context
Org Context is set per business / line of business and extends Global.
- Open My Account → select the business in the left panel.
- Open the Context tab.
- The Inherited from Global box shows your Global Context. Leave Include in Org Context on to include it, or turn it off to leave it out for this business.
- Under Additional Org Context, add this business’s own rules. You can:
- Add brand-new instructions that don’t exist globally.
- Change a Global rule for this business by stating the new version explicitly.
- Click Save. The page shows who last saved it and when.
Setting Account Context
Account Context is the narrowest scope. Each connected account has its own Account Context page.
- Open My Account → select a business → in the Platforms tab, click the Account Context icon on the account’s card.
- The Inherited Context box shows the Global and Org text this account inherits. Leave Include in Account Context on to include it, or turn it off to write a fully separate block.
- Under Multi-account context, write rules shared by related accounts, and pick those accounts with Choose Accounts under Applies to these accounts. This block must apply to two or more accounts.
- Under Additional Account Context, write rules for this account only. Examples:
- “For account X, attribution model is last-non-direct click; ignore view-through conversions.”
- “Campaigns prefixed with
_TEST_are experiments—exclude from rollups.” - “KPI for app-install campaigns here is CPI, not CAC.”
- Attach knowledge documents—taxonomy sheets, brand books, partner agreements—so the AI can read them when this account is in scope. See Knowledge Documents.
- Click Save.
Composability
You don’t have to pick between “inherit everything” or “write everything fresh.” At any level you can:
- Inherit + extend — keep the parent’s text and add more rules below it.
- Inherit + adjust — keep the parent’s text and state a changed rule explicitly, e.g. “For this business, …”. The parent’s version is still included, so make it clear which one applies here.
- Disable inheritance — for unusual accounts, turn off the include toggle and write a fully separate block.
The Learn about context button on each context page walks through these patterns with examples.
How to Tell It’s Working
Start a new chat scoped to the account and ask about an acronym, KPI, or campaign exclusion you defined. The answer should reflect your wording.
If something didn’t apply, two common culprits are:
- The chat or workflow was scoped to a different business / account than where you saved context.
- A narrower level (Org or Account) says something different, or has its include toggle off, so your broader text isn’t read.
Best Practices
- Start global, narrow down. Encode shared vocabulary once at Global; reserve Org and Account context for true exceptions.
- Be concrete about KPIs. Spell out the formula, the data source, and any exclusions.
- Name campaign conventions. If you have a naming scheme like
[Geo]_[Funnel]_[Brand]_[Date], write it down—Aliveo will use it to auto-tag campaigns. - Document exclusions. “Ignore campaigns containing the string
_archive” is more useful than a list of campaign IDs that goes stale. - Describe your custom data. When you connect custom data, each column gets a type (Date, ID, Metric or Category) and a description, and metrics also get an aggregation (Sum or Mean). Clear column descriptions make your context rules easier for Aliveo to apply.
- Revisit periodically. Context is living text; the last-saved details help you know when it’s time for a refresh.
For the architecture behind cascading context, see How Context Works.