This week is Unbound. If you want to see me, check the New Breed booth or New Breed lounge.
For subscribers to spotter, If I am able, I will help you use AI to create a custom API app or UI card.
SPOTTER | Your Hubspot Helper
📢 Announcement
HubSQL API
This one is huge for anyone working on big data projects in HubSpot. This will likely be a very useful tool for untangling associated records, cross filtering on associations, and producing database-ready exports from HubSpot.
✅ ⚠️ Trap
Mistake to avoid before it causes chaos.
Don’t Use Brands if You Need Strict Governance
I have seen this come up several times this year. Whether it’s a merger, acquisition, or the organic outgrowth of a new business unit, a lot of HubSpot users seem to gravitate towards the “Multi-Brand” feature.
Here is what it is for:
One business with multiple DBAs or names
Different visual styles
Governance over assets like forms, landing pages, CTAs, and workflows.
Here is where you’re going to get in trouble
Team access & permissioning
Overlapping records
Brands is fine UNLESS you need both business units to operate autonomously without sharing any records.
If brand A and Brand B both have a relationship with a given contact, you are going to need complex enterprise properties, often with one per each brand, and even then, there really is no way to filter notes and email activities.
If your leadership needs reporting that “rolls up” both business units while frontline teams are kept separate, go with multi account.
👋 Need a Spot?
Want help cleaning up your HubSpot portal or setting up something smarter?
Let’s talk about what hands-on help could look like for your team.
