Multiple Brands in HubSpot: One Account or Separate Accounts?

Running two or more brands inside one HubSpot account can save money and keep teams aligned.

It can also create reporting confusion, subscription headaches and messy data if you set it up without a plan.

This guide walks through how HubSpot's Brands add-on works, when one account makes sense, and when separate accounts are the better call.

What the Brands add-on actually does

HubSpot's Brands add-on lets you define multiple brands inside a single account.

When you purchase it, you keep your existing account brand and can add more brands from the Multi-Brand settings page.

Each brand gets its own identity inside the CRM, and a Brands property is created so you can tag contacts, campaigns, forms, emails and reports with the brand they belong to.

HubSpot documents this with an example of a car manufacturer running two brands, Motr and Engn, under the same marketing department.

Customers can belong to one brand or both, and campaigns for each brand run separately HubSpot Brands documentation.

That shared-department scenario is the sweet spot for the add-on: one team, one toolset, several customer-facing identities.

Key capabilities to know before deciding

Tracking codes per brand

Each brand is associated with its own unique tracking code.

That means you can display different cookie policy banners on different pages, which matters when your brands operate in different regions or under different privacy positions.

HubSpot notes that separate tracking codes do not affect reporting HubSpot Brands documentation.

If your requirement is genuinely separate analytics properties, that is a different conversation than brand separation inside HubSpot.

Subscription pages and email preferences

You can customize email subscription pages per brand, so subscribers see that brand's preference center instead of a generic account-level page HubSpot Brands documentation.

This is one of the strongest practical arguments for the add-on when your brands email overlapping audiences.

Reporting and filtering by brand

Once brands exist, you can build single-object reports using the Brands property HubSpot Brands documentation.

You can also associate existing dashboards and reports with a brand, and filter dashboards using the business unit filter.

You can also filter the reports list itself by brand and use the Set brand action to assign selected reports in bulk HubSpot reports documentation.

One caution from the reporting documentation: report and dashboard access does not override CRM record, data source or field permissions.

Users without access to underlying records may see partial data, a blank report or an error HubSpot reports documentation.

If your brands have separate sales teams with restricted record visibility, brand-tagged reports will not magically expose or hide data beyond those existing permissions.

One account or separate accounts: the real tradeoffs

There is no universal answer, but the decision usually comes down to four questions.

• Who owns the brands? If one marketing department runs both brands, the add-on fits well. If the brands have separate leadership, budgets, contracts or even separate companies, separate accounts usually reduce friction.
• How much do audiences overlap? Shared contacts are easier to manage in one account, where a single contact record can belong to multiple brands HubSpot Brands documentation. In separate accounts, the same person exists twice and you own the sync problem.
• Do you need hard separation? Different sales pipelines, different user access models, or contractual data separation push you toward separate accounts. The Brands add-on organizes data; it does not replace your permission structure.
• What is the cost picture? Separate accounts mean separate subscriptions. The add-on is an additional purchase on top of your existing portal. Price both paths against the operational cost of whichever structure creates more manual work.

A useful middle case: brands that share marketing but sell through different teams.

You can run brand-tagged campaigns and reports centrally while using teams and pipelines to keep sales operations distinct.

That works only if your permission setup is deliberate, so audit it before committing.

Setting up a second brand in practice

HubSpot's documented flow is straightforward.

Create the brand in Multi-Brand settings, then assign a campaign to it from the campaign's Brand dropdown.

Existing contacts get assigned through the Brands property, which can then power lists and workflows for segmentation HubSpot Brands documentation.

HubSpot itself describes this example as a simple process that is not exhaustive, and notes that brand configuration varies by organization HubSpot Brands documentation.

Treat the mechanics as easy and the governance as the hard part.

Before you create the second brand, decide:

• Which existing contacts, if any, get backfilled with the new brand value, and who approves that mapping.
• Which lifecycle and pipeline stages apply across brands, and whether any stages differ.
• Who owns brand-tagged reports and dashboards.
• How new records get their brand value by default, whether through forms, imports or workflows.

Deletion behavior you should know upfront

Brands are not trivially reversible.

If you delete a brand, the brand disappears but its data is not deleted; existing data, assets and settings move into the account brand.

Subscription types move into the account brand and opt-outs to those types are kept.

However, unsubscribes from the deleted brand are removed and are not converted into account-brand opt-outs HubSpot Brands documentation.

That last detail matters for your email opt-out records.

If you ever consolidate brands, plan the subscription handling before deleting anything, and verify how your specific subscription types and opt-out records will behave.

Also note that Brands cannot simply be turned off; removing the feature requires contacting your Customer Success Manager to cancel the add-on HubSpot Brands documentation.

Common failure modes and how to avoid them

• Inconsistent brand tagging. If some contacts get the Brands property from forms and others never do, brand-filtered reports will undercount. Define the default assignment path and audit for untagged records.
• Assuming tracking codes split analytics. Unique codes control cookie banners, not reporting separation HubSpot Brands documentation. If you need distinct web analytics, verify what your analytics stack provides separately.
• Overloading one account. The add-on works best when brands share operations. If every process needs a brand-specific exception, the maintenance cost can exceed the subscription savings.
• Ignoring access interactions. Because report access does not override record and field permissions HubSpot reports documentation, test brand dashboards as the users who will actually view them.

A practical decision path

Work through the same four questions in order.

1. Confirm who owns each brand and whether leadership, budgets or contracts are shared.
2. Test audience overlap: if the same people buy from both brands, one account with the Brands add-on keeps a single source of truth for contacts, subscription preferences and cross-brand reporting.
3. Check whether you need hard separation in pipelines, access or data handling; if so, separate accounts give you clean isolation at the cost of duplicate administration and no shared contact view.
4. Pressure-test with reporting. Sketch the dashboards each brand owner needs and confirm you can build them with the Brands property and dashboard filters HubSpot Brands documentation. If a required report cannot be expressed cleanly in one account, that is a real signal toward separation.

Verify operational details for your plan and configuration with HubSpot directly, including add-on availability, pricing and limits.

These vary by subscription and can change.

Whichever structure you choose, document the brand-assignment rules so the data stays trustworthy as the team grows.

Where this fits in your revenue operations

Brand structure is really a data-governance decision.

The same discipline applies to how you reconcile subscription data with finance systems.

For keeping HubSpot data aligned with billing systems, see our subscription data vs finance mismatch guide.

If brand-tagged workflows are part of the plan, see our inbound lead routing workflow guide for the mechanics.

How Meshline can help. Connect automation, Organic Marketing (demand generation), and customer lifecycle management (Revenue Intelligence).

Bring topic planning, content publishing and performance feedback into the conversation about your workflow. Book a Meshline demo.