| 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.
Overview
Context Hub gives agents the shared information they need to understand your business and follow your brand and creative rules. Instead of adding the same instructions to every prompt, configure them once and make them available wherever they're relevant.
For example, you can:
- Define what terms such as active customer or high-value account mean for your business.
- Add logos, fonts, product catalogs, and other brand assets.
- Set writing, email, and image guidelines for generated content.
- Connect advertising platforms, email providers, and digital asset managers.
Accurate context gives agents better information to work from, so their results require less editing and stay more consistent across your team.
Where Context Hub is used
Context Hub provides shared context to Agents, Ad Studio, and Lifecycle Studio. Each product uses the context relevant to its workflows.
| 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 add context, you can use Agent scope to make it available only to specific products, or leave it unscoped to make it available to every supported product.
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.
What you configure in Context Hub
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.
How Context Hub fits into 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.
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.