Business Context is a shared memory for your team, built into the Supermetrics MCP server, and used by AI tools and Supermetrics Studio. Save a preference once, in an AI tool or Supermetrics Studio, and your whole team gets it in every future conversation.
Without Business Context, you repeat the same instructions in every new chat: which time zone to report in, which accounts belong to which client, or why a dip in your data isn't a real problem. Business Context saves that guidance once, so nobody has to repeat it.
Where you can use it
Business Context works in AI chats built on the Supermetrics MCP server, including Claude and ChatGPT, and in Supermetrics Studio. You'll need an existing connection between Supermetrics and an AI tool or Supermetrics Studio to use it.
What you can save
Save any guidance you'd otherwise repeat. Common examples include:
Reporting conventions: The time zone, currency, or attribution model to use, and the metrics that matter most to you.
Analysis rules: Which campaigns to exclude, how to segment data, or which account is the one to report on.
Naming conventions: How you name campaigns and ad groups, and what the parts mean.
Brand and tone: How to describe your brand, and any words to use or avoid.
Client mapping: For agencies, which accounts across Google Ads, Facebook Ads, and other platforms belong to each client.
Known events: Background on a rebrand, tracking outage, or budget change, so a genuine event doesn't get flagged as a new problem.
Save the rule, not the report. Business Context works best for short, reusable guidance, not for pasting in whole documents or briefs.
Where context applies
You can save context at 3 levels, so it shows up only where it's relevant:
Your whole team: Applies everywhere, for example, get revenue reported always in EUR.
A specific data source: Applies whenever you work with that platform, for example, break out Advantage+ campaigns separately for Facebook Ads.
A specific account: Applies to one advertiser or account, for example, this client reports last-click attribution only.
A client that spans several accounts and platforms doesn't fit neatly into one level. For agencies, a good approach is a team-level note that lists which accounts belong to each client.
How it works
Tell your AI tool or Supermetrics Studio the preference you want to save, as part of a normal conversation. It offers to save the note, and sometimes suggests saving one when you state a rule or correct its approach.
From then on, when you explore your data sources or accounts, the AI tool applies the guidance your team already saved, without you having to ask.
To change or remove a saved note, ask your AI tool to update or delete it. Deleting a note is permanent, so it confirms first.
Examples
Reporting conventions for an in-house team: Say your team always reports Shopify data in your store's local time zone, not in UTC. Tell your AI tool once:
Report Shopify data in Oslo time, not UTC. Remember that.From then on, every teammate who asks for a Shopify report gets it in Oslo time, without asking again.Client mapping for an agency: Say you report on a client, Acme Retail, across 5 ad accounts on 3 platforms. Tell your AI tool once which accounts belong to Acme Retail. From then on, when anyone on your team asks about "the Acme Retail account," your AI tool knows exactly which accounts to use, instead of guessing.
Who can manage saved context
Saving, changing, or deleting context is limited to team owners, admins, and editors. Everyone on your team benefits from context that's already saved, but only those roles can add or change it.
Business Context follows the same account-access rules as your data. If your access to an account is restricted, that account's saved context is restricted too.