| Audience | Platform admins, data teams, marketing teams, and creative teams |
| Prerequisites | At least one agent product enabled (Agents, Ad Studio, or Lifecycle Studio), and the Configure Agents grant to make changes |
Context Hub is the shared place to configure the business knowledge, brand rules, and connections that agents use across Hightouch. Configure them once, then each agent product uses the pieces it needs.
What you'll learn
- What Context Hub is
- What information belongs in Context Hub
- How Context Hub fits into an agent's context
- Which products use Context Hub
- Who manages Context Hub
- When to configure it
Overview
Context Hub is Hightouch's shared context layer. Instead of repeating business definitions, brand guidance, and creative rules in every prompt or workflow, you configure them once and agents reuse them wherever they're relevant.
For example, you can:
- Define business concepts, such as what qualifies as an active customer or a high-value account.
- Upload brand assets, such as logos, fonts, and product catalogs.
- Document writing style, image-editing rules, and email guidelines.
- Connect advertising platforms, email providers, and digital asset managers.
The more accurate your context is, the more accurate your agents become. When an agent understands your business, your brand, and your rules, it produces results that need less editing and stay consistent across your team.
What Context Hub stores
Context Hub stores reusable information that should apply across many tasks, instead of being repeated in individual prompts:
- Business definitions and rules
- Brand profiles and creative guidelines
- Product catalogs and reference assets
- Copy examples and writing guidance
- Email and image guardrails
- Platform connections
- Memories that agents learn and you confirm
Each item becomes available to the agent products that need it. You decide whether an item applies everywhere or only to specific products by setting its Agent scope.
Context Hub is one layer of an agent's context
Context Hub helps agents understand your business, but it isn't everything an agent uses to answer a request. Every request combines three layers:
| Layer | What it covers | Where you set it up |
|---|---|---|
| Access | What the agent can query | Sources, Models, the Customer Studio schema, permissions, and Context Hub connections |
| Context Hub | What your business means | Business context, brand guidance, creative assets, rules, and memories |
| Task | What the agent should do | The prompt, uploaded files, reports, or custom agents |
This distinction helps when you're troubleshooting agent output:
- If the agent can't find the data it needs, update the Access layer.
- If the agent has the data but interprets it incorrectly, update Context Hub.
- If the request itself is unclear, improve the Task.
Context Hub stores both the information you write and the memories that agents learn and you approve. Agents don't load everything for every request. They retrieve the context most relevant to the task, so clear names and descriptions make it easier for them to find the right information.
Which products use Context Hub
Different products use different parts of Context Hub:
| Product | Uses |
|---|---|
| Agents | Business context, business rules, skills, and memories |
| Ad Studio | Brand profiles, creative guidelines, logos, fonts, styles, product catalogs, copy examples, research signals, and advertising-platform connections |
| Lifecycle Studio | Business context, brand guidance, copy examples, styles, email rules, image guardrails, and ESP connections |
When you create a context item, set its Agent scope so it's available only to the products that need it, or leave it unscoped so every supported product can use it. See Teach agents your business for more about agent scope.
The audience builder in Customer Studio uses your Customer Studio schema, not Context Hub. To change the audiences it generates, update your schema (models, relationships, traits, and events) instead of adding a Context Hub item.
Who manages Context Hub
Different teams usually own different parts of Context Hub:
| Role | Responsible for |
|---|---|
| Platform admins | Permissions, governance, and workspace configuration |
| Data teams | Business definitions, metrics, rules, and platform connections |
| Marketing and creative teams | Brand profiles, voice, creative assets, styles, and content rules |
| Everyone else | Testing agent output and flagging missing or incorrect context |
Anyone who edits Context Hub needs the Configure Agents grant. See Roles for role details, and Agents data governance for how data permissions affect agents.
Assign a single team or owner to maintain shared context over time. Regular reviews keep outdated or conflicting definitions from accumulating.
When to configure Context Hub
You don't need to document your entire business before you use agents. Start with the workflow you're implementing today, then expand your context as agents hit gaps or make incorrect assumptions.
Some context is worth configuring before you begin:
- Brand assets and creative guidelines, before generating ads or emails
- Business definitions, before asking agents to analyze your data
- Platform connections, before analyzing campaign performance
See Set up your context for a recommended onboarding sequence.
Related articles
| Go here | To |
|---|---|
| Set up your context | Decide what to configure first |
| Connections | Connect advertising platforms, ESPs, and digital asset managers |
| Teach agents your business | Add business context, skills, memories, and research signals |
| Set content and creative rules | Configure brands, styles, product catalogs, copy examples, email rules, and image guardrails |
Next steps
- Follow Set up your context to configure Context Hub for your first workflow.