| Audience | Platform admins, data teams |
| Prerequisites | A data warehouse connected as a source, Customer Studio schema configured, Agents enabled |
Context Hub is where you define your brand identity, metric definitions, content rules, and channel connections so agents act correctly and consistently across products.
What you'll learn
- Access Context Hub and understand who can configure it
- See where Context Hub fits in the setup and ongoing maintenance workflow
- Create brand profiles to organize context and assets by brand
- Provide organizational context, best practices, and guardrails
- Connect marketing channels and email service providers
Overview
Context Hub is Hightouch's shared context layer. It brings together the knowledge, brand assets, and marketing connections that Agents, Ad Studio, and Lifecycle Studio rely on. Instead of managing this configuration separately in each product, you configure it once in Context Hub and it applies everywhere.
The quality of agent output depends directly on the context you provide. Define your metrics, upload brand guidelines, set guardrails, and connect your marketing channels in one place. Every agent across your workspace references the same context.
Context Hub is organized into three pages:
- Brands — manage brand profiles, business context, logo files, and fonts
- Context — provide organizational knowledge, best practices, guardrails, and memories
- Connections — connect ad platforms and email service providers
Access Context Hub
To open Context Hub, click Context Hub in the left navigation. From there, select Brands, Context, or Connections.
Only users with the Can this role configure Agents? permission can modify Context Hub. See Agents overview for more on permissions.
How Context Hub fits into Hightouch
Context Hub sits between data setup and agent execution. You configure it during initial workspace setup, then return to it periodically as your business evolves.
During setup
After connecting your data warehouse and configuring your Customer Studio schema, Context Hub is the next step before your team starts using Agents, Ad Studio, or Lifecycle Studio.
| Step | What to do | Where |
|---|---|---|
| 1 | Connect your data warehouse | Sources |
| 2 | Set up your schema | Customer Studio |
| 3 | Teach Hightouch about your business | Context Hub |
| 4 | Use agents across products | Agents, Ad Studio, Lifecycle Studio |
During ongoing maintenance
After setup, you return to Context Hub when:
- Agent outputs need refinement — add metric definitions, update guardrails, or correct assumptions saved as memories
- You launch a new brand or sub-brand — create a new brand profile with its own context, logos, and fonts
- You add a marketing channel — connect a new ad platform or ESP so agents can analyze its performance data
- Business context changes — update brand guidelines, campaign formats, or organizational rules
What flows in and out
Context Hub receives data and configuration from your warehouse and marketing tools, then makes that context available to downstream products.
| Direction | What | Where it connects |
|---|---|---|
| In | Warehouse data (via your connected source and schema) | Sources, Customer Studio schema |
| In | Campaign performance data from connected channels | Ad platforms (Meta, Google Ads, TikTok, etc.) and ESPs (Braze, Iterable, etc.) connected in Connections |
| Out | Brand profiles, context cards, guardrails, and memories | Agents chats and reports |
| Out | Brand guidelines, logos, and fonts | Ad Studio, Lifecycle Studio |
Brands
The Brands page manages brand profiles, logo files, and fonts. Logo files and fonts are shared across Ad Studio and Lifecycle Studio.

Brand profiles
Brand profiles let you organize context and brand assets by brand. For example, a company with both a consumer brand and a B2B brand can create separate profiles, each with its own context, logo files, and fonts. Use the brand selector dropdown at the top of the page to switch between profiles.
To create a brand profile, go to Context Hub, then Brands, and click Add brand profile. Each profile has a Name and an optional Business context field where you provide a short summary of the business, target market, and value props. The business context gives agents high-level background about the brand when generating creative content. You can refine this and add brand guidelines, logos, and fonts after creating the profile.

Brand guidelines
Upload brand guidelines that the agent references when generating creative content. Brand guidelines define visual identity, tone of voice, and style rules. Click Upload to add a brand guidelines document.

Logo files
Upload logo files that Ad Studio and Lifecycle Studio can reference when generating creative content. Logos are shared across both products, so you only need to upload them once.
Fonts
Add fonts for use in generated content. Click Add font to add a new font. Context Hub supports four font types:
- Web safe fonts — standard fonts available on most devices (for example, Helvetica, Arial)
- Google Fonts — fonts loaded from Google Fonts (for example, Inter, DM Sans, Open Sans)
- Custom font URL — URL-based custom fonts hosted elsewhere
- Custom font files — upload font files directly (.ttf, .otf, .woff, .woff2)
Fonts are shared across Ad Studio and Lifecycle Studio.


Context
The Context page provides the agent with background knowledge about your organization, metrics, and workflows so it can return more relevant answers. Context is organized into four tabs: Context, Best Practices, Guardrails, and Memories.
Context cards
Context is organized into named cards, each containing instructions or definitions the agent should follow. Click Add context to create a new card.
Each context card includes a brand profile selector. Assign a card to one or more brand profiles to scope it to those brands, or leave it unassigned to make it available to all profiles.
Common context cards include:
- General — how the agent should behave, which data tables to prioritize, and any global instructions
- Metric definitions — your organization's specific definitions for metrics like LTV, attribution windows, conversion rates, or engagement scores
- Campaign formats — templates or formatting rules for campaign briefs, reports, or other structured outputs
- Email copy guidelines — rules for generating or reviewing email content
You can also upload files directly within a context card. Files are useful for qualitative context that's hard to express as text instructions, like planning documents, brand guidelines, or example reports the agent should reference.

Best practices
Best practices are rules the agent applies when analyzing and fixing email HTML for cross-client compatibility. Each rule category contains individual rules that can be toggled on or off. Disable any rules that don't apply to your templates.
Rule categories include:
- Compatibility — rules for cross-client rendering consistency
- Mobile Responsiveness — rules for responsive email layouts on mobile devices
- CSS Patterns — rules for CSS usage that works across email clients
- Dark Mode — rules for dark mode support and fallback styling
- Accessibility — rules for accessible email markup and content
- Structure — rules for email HTML structure and organization
- Custom — add your own rules for organization-specific email requirements

Guardrails
Guardrails control what actions the agent is allowed to take when modifying images in your campaigns.
Each guardrail can be toggled on or off independently:
- Edit text — change text burned into images, like headlines, prices, or calls-to-action
- Resize — resize images to fit different formats or aspect ratios
- Blend elements from your content library — replace or combine visual elements using only images from your approved content library
- Adjust colors and styling — change colors, backgrounds, and visual styling of existing elements
- Generate new visual elements — create new objects, change scenes, or generate compositions beyond your existing assets
Click Disable all to turn off all image modification capabilities at once.

Memories
Memories are saved facts and definitions from conversations. When an agent makes an assumption during a chat — like how to define a metric or interpret a data field — it can flag that assumption. You can then save it as a memory so future conversations reference it for consistency.
Memories are created in two ways:
- From chats — when the agent flags an assumption during a conversation, you can save it as a memory. For example, if the agent assumes a specific definition for cart abandonment, that definition can be saved so all future conversations use the same one.
- Explicitly via chat — ask the agent to create memories directly. For example, upload a file containing metric definitions and ask the agent to create memories, which you can then save.
Memories are grouped by scope:
- Workspace — memories that apply globally across all agents and conversations
- Parent model — memories associated with a specific parent model
Admins can view and delete memories in the Memories tab. Memories are optional — if you prefer to manage all agent knowledge through context cards, you can rely entirely on those instead.


Connections
The Connections page connects your marketing tools and ad accounts so the agent can analyze campaign performance data alongside your warehouse data. This page consolidates connections that were previously managed separately in Ad Studio and Lifecycle Studio into a single view.
Channels
Under Connected, you'll see any channels already set up. Under Available, click the + button next to a platform to connect it.
Available ad platforms include:
- Facebook Ads
- Google Ads
- Bing Ads
- Snapchat Ads
- LinkedIn Ads
- TikTok Ads
- The Trade Desk
- Pinterest Ads
Available ESPs and marketing platforms include:
- Attentive
- Braze
- Iterable
- Klaviyo
- Salesforce Marketing Cloud
Sources may take up to 30 minutes for the initial data sync to complete after you connect a channel.

Email service providers
Below the ad platform connections, you can connect an email service provider to import email templates. Select your ESP from the dropdown and provide the integration name to complete the connection. Once connected, you can click View Templates next to any integration to browse imported templates.
