Insider One’s multi-workspace architecture lets each brand in a group operate with its own isolated data and governance, while sharing common underlying infrastructure. Group-level reporting is aggregated across brand workspaces, and cross-brand controls, such as shared caps or unified audience logic, are achieved through a group-level unification layer that sits atop the isolated workspaces, rather than by merging their underlying data.
A group operating multiple brands needs each brand to control its own data, campaigns, and access, without duplicating infrastructure per brand and without losing the ability to see or act at the group level when required. Insider One’s architecture separates these two concerns: brand-level isolation is achieved by giving each brand its own workspace, while group-level needs (reporting, shared caps, unified audiences) are handled by a separate unification layer that reads across workspaces, rather than collapsing brands into a single shared data pool.
This article covers the answers to the questions below:
Does isolating brand data mean each brand needs its own infrastructure?
Can a group see performance across all its brands in one place?
Can brands share control, such as a frequency cap, without merging their data?
Workspace architecture & brand isolation
Each brand in a group operates in its own Insider One workspace. A workspace contains that brand’s customer profiles, segments, campaigns, and journeys, as well as its user access and role permissions, independent of any other brand’s workspace in the group.
Layer | Isolated per brand? | Notes |
|---|---|---|
Customer data | Yes | Each workspace has its own customer profile store and segments. |
Campaigns & journeys | Yes | Built, managed, and governed independently per brand. |
User access & roles | Yes | Role-based permissions are scoped per workspace. |
Underlying infrastructure | No | Shared across brand workspaces; see below. |
Shared infrastructure
While each brand’s data and governance are isolated at the workspace level, all brand workspaces in a group run on the same underlying Insider One platform infrastructure. A new brand can be onboarded into its own workspace without standing up separate infrastructure, and platform-level capabilities, such as channels, AI features, and integrations, are available consistently to every brand workspace in the group.
Group-level reporting aggregation
Two paths are available for rolling brand-level metrics up to a group view:
Insights Agent: Queries and consolidates data across brand workspaces into a single dashboard view, giving a group-level read without opening each brand’s panel separately.
API-based aggregation: For programmatic or external reporting, metrics can be pulled from each brand workspace via API and aggregated at the group level in the group’s own reporting or BI stack.
Both paths read from the same brand-workspace data, so a dashboard view via the Insights Agent and a programmatic export via API reflect the same underlying metrics. The choice is about where the aggregation happens, not which numbers are used.
Cross-brand unification for shared controls
Some group-level requirements go beyond reporting and need brands to actually coordinate behavior, for example, a shared frequency cap across brands or de-duplicating offers so a customer isn’t served conflicting promotions from two brands at once. Because each brand’s data stays in its own workspace, this is achieved with a group-level unification (GLU) pattern rather than by merging the brands’ data pools:
A lightweight lookup table is synced centrally across the relevant brand workspaces, acting as a shared ceiling or shared state that every brand’s workspace can read.
Liquid logic in each workspace reads that shared state to enforce cross-brand rules, such as a shared cap or offer de-duplication, at the point a message or offer is evaluated.
This group-level unification approach is the same underlying pattern used for cross-brand frequency capping and cross-brand offer de-duplication elsewhere in the platform. It’s a proven, repeatable mechanism for group-level coordination on top of isolated brand workspaces, not a one-off workaround.
Governance model
Because isolation happens at the workspace level, each brand retains control over its own users, roles, data, and campaigns, while the group retains visibility and coordination ability through the reporting and unification layers described above. This keeps day-to-day brand operations independent while still giving group functions (marketing operations, compliance, group reporting) a consistent way to see and act across brands where needed.