With Brands or business units to separate assets and subscriptions, pipelines per business line, subscription types per brand and send exclusions with lists. That way each brand of a company in Chile or Latin America has its own forms, emails, domains and reports without losing the full view of the customer in one portal.
| Need | Tool |
|---|---|
| Forms, emails, domains and subscriptions per brand | Brands, formerly business units |
| Different sales processes per line | One pipeline per line, with access by team |
| A send from one brand must not reach another brand's customers | Subscription types and lists in "Don't send to" |
| Each team sees only its own assets | Teams and asset partitioning |
| Reports per brand without duplicating contacts | Brand property and dashboard filters |
The native tool is Brands, the current name for business units. It is a Marketing Hub Enterprise add-on: under Settings > Brands > Multi-Brand, a super admin creates each brand and HubSpot generates the Brands contact property, in which a contact can belong to several. Each brand has its own brand kit and one additional brand domain.
You can associate forms, marketing emails, pages, subscription types, campaigns, social accounts, domains, workflows, documents, quotes and invoices with a brand. Each brand sees and uses its assets, and subscription preferences are shown per brand.
It is solved with four pieces from lower tiers. Pipelines per business line: Starter lets you create them and, with Professional or Enterprise, you restrict each one to a team from Actions > Manage access. Teams and asset partitioning: templates, sequences and pipelines from Professional; forms, emails, workflows and reports in Enterprise.
Subscription types from Settings > Marketing > Email > Subscription Types, available from Marketing Hub Starter, with the brand name. And a custom multiple-checkbox Brand property on contacts, companies and deals, required when the record is created, that feeds lists, dashboard filters and sends.
The first barrier is the subscription type: each brand sends only to contacts subscribed to its type. The second is the exclusion list: in every send, the Don't send to field accepts lists, for example "Active customers of brand B", which stay out even if they meet the rest of the criteria.
The third is reputation. Each brand can send from its own domain connected under Settings > Content > Domains & URLs > Email Sending, with its DKIM, SPF and DMARC records. The Don't send to unengaged contacts option is on by default and protects the shared reputation.
The rule is one contact, many brands. A customer who buys from two brands of your group is one record with two values in the brand property and two subscriptions, not two contacts. Duplicating contacts per brand breaks email deduplication and makes it impossible to know what that customer is worth to the group.
Reports per brand are built with the brand property as a filter: one dashboard per brand and one group dashboard without a filter. Companies in Chile and Latin America with several legal entities usually also need a billing company property, separate from the commercial brand.
Six steps. With the Brands add-on or without it, the order is the same.
Make a table per brand: its own forms, emails, pipelines, teams, domains and reports. What is not on the table is shared, and sharing is normal for contacts and companies.
With the add-on: Settings > Brands > Multi-Brand > Create new Brand, which generates the Brands property. Without it: a multiple-checkbox Brand property on contacts, companies and deals, required on creation.
Settings > Data Management > Objects > Deals > Pipelines > Create pipeline. One pipeline per distinct sales process, not per rep or region. Restrict access by team with Manage access.
Settings > Marketing > Email > Subscription Types > Create subscription type, with the brand name. Each form subscribes only to its brand's type.
In every email, choose the brand's subscription type, add lists under Don't send to and keep the unengaged contacts exclusion on. Connect one sending domain per brand.
Create teams per brand under Users & Teams, partition assets with Actions > Manage Access and build one dashboard per brand with dashboard filters on the brand property.
One portal per brand: duplicate contacts, repeated integrations and nobody who sees the whole customer.
One pipeline per rep instead of one per process, with stages nobody compares.
One subscription type for every brand: unsubscribing from one newsletter unsubscribes from all.
A single sending domain for the whole group, with reputation shared across brands.
30 minutes with Roberto. No demo and no access to your CRM.
We inventory the portal, separate brands or business units, redesign pipelines per line, organize subscriptions and permissions, and leave everything documented and in your name. Afterwards, Managed or Dedicated HubSpot keeps the order with response times and alerts.
Brands, pipelines per line, subscriptions per brand and permissions by role, with every change documented.
See the serviceIn 10 hours we inventory assets, pipelines, subscriptions and permissions, and tell you what to organize first.
See the DiagnosticWe tell you whether the Brands add-on is worth it for your case or whether order is achievable with what you already pay for.
See LicensesThe guarantees that apply
Workflows, integrations, code and keys documented and in your name. If you change partners, you lose nothing.
We check the numbers your management uses against the records, with definitions and sources documented.
We put them in writing because they are what we control.
Not always. Pipelines per line, subscription types per brand, teams and a brand property solve most of it. The add-on, which requires Marketing Hub Enterprise, adds brand kits, domains and preferences per brand.
Yes. The Brands property accepts several values, and so does a custom multiple-checkbox property. It is the right way: one record per person, with all their brands and subscriptions.
It depends on the tier: Starter lets you create custom pipelines and the limits rise in Professional and Enterprise. Restricting a pipeline to a team requires Professional or Enterprise.
With subscription types per brand, exclusion lists under Don't send to and one sending domain per brand. The unengaged contacts exclusion, on by default, also protects reputation.
Almost never. It duplicates contacts, integrations and licenses, and loses the group view of the customer. Across Chile and Latin America we see that one portal with separate brands and permissions per team is cheaper and easier to operate.
The commercial brand and the company that invoices are different things. A billing company property helps, especially when the ERP needs to know which entity each deal belongs to.
Designs the CRM architecture, integrations and operation of each account. He writes these guides from what he sees every week in HubSpot portals of B2B companies across Chile and Latin America.
Meet the teamWe review one concrete problem, its impact and your starting point. No demo and no access to your CRM.
