How it works
Measured separately. Reported together.
The structure is chosen at onboarding, so the data is right from day one.
1
Choose
Pick multi-product for one company, or multi-brand for many.
2
Configure
Each product or brand gets its own site, competitors and prompts.
3
Monitor
Every one is tracked separately across all 10 engines.
4
Roll up
Workspace View combines them into portfolio KPIs and trends.
5
Scan
Movers surface what gained and lost ground, per product or brand.
Separate tracking in. One honest portfolio read out, without losing the detail.
The hard part we solved
The tempting shortcut is to average everything and call it a portfolio view. That produces a number that is technically correct and strategically useless, because a portfolio is not one brand with more pages. Each product has its own buyers, its own prompts and its own competitive set. Your identity product loses to a different company than your cloud product does. So nothing is blended at the measurement layer. Every product or brand is monitored as its own entity, with its own library and its own rivals, and the roll-up happens only at the reporting layer, where it belongs.
The second decision is the one you make at onboarding, and it matters more than it looks. Multi-product is for one company running several products or solutions, where each needs its own dashboard but the org shares positioning and often shares a domain. Multi-brand is for agencies and holding companies tracking genuinely separate businesses, each with its own site and its own competitors. The two look similar in a screenshot and behave differently underneath, in how competitors are inherited, how prompts are scoped and how the roll-up is framed. Getting that structure right on day one is why the numbers still make sense a year later.
