Portfolio-level AI visibility, without flattening the brands.
For operating groups and PE-backed portfolios running four to twelve ecommerce brands: one rollup for the board slide, independent tracking, query banks, and approvals for every brand inside it. One contract, one SSO, one DPA — and the portfolio spreadsheet gets retired.
Three problems every central growth team hits.
Each brand has its own answer surface.
The grooming brand's query bank is not the supplement brand's. Blurring six brands into one "portfolio metric" destroys the signal. Tracking stays per brand; only the rollup is shared.
Central IT asks the questions first.
SSO, DPA, audit logs, least-privilege access. The Agency & Enterprise contract arrives with the paperwork in motion: Okta, Google, or Azure AD SSO, per-brand role scoping, and a security review list on file.
Brand GMs don't want a dictator.
HQ pushing PDP changes without brand approval is how a group CMO loses a brand team. Brand-team approval is the default; central override paths exist and leave an audit trail every brand can see.
A portfolio of brand pings is still just pings.
Running a brand tracker like Brandlight or Scrunch across six brands gives the central team six mention counts (per their sites, as of mid-2026 — both are brand-level by design). What it can't give a portfolio operator: which sister brand's SKUs are cannibalizing the other's in overlapping categories, which brand's PDP debt is dragging the group average, and what each brand team should ship next sprint.
SKU-level tracking answers those because the rollup is built from product-level data, not brand pings. Comparisons: vs Brandlight · vs Scrunch.
Central reads the rollup. Brands work their queues.
Each brand, its own store
Shopify-native first; channel connectors per brand. Every brand keeps its own query bank, engines, and approvers.
Two scores per product
Citation and agent-readability scores per product, rolled up per brand, then per portfolio. How tracking works.
Brand vs. brand
Internal benchmarks across the portfolio: who's gaining citations, who's overdue, where sister brands collide in the same answers.
Approvals with audit trails
Brand teams approve their own diffs by default. Central override for catalog-wide fixes is configurable — and logged.
Portfolios run the Agency & Enterprise tier.
One brand piloting on Starter or Growth is a sensible first step; the portfolio posture — rollups, SSO, brand isolation, consolidated billing — lives on Agency & Enterprise. Pricing follows brand count with discounts as the portfolio grows, and there is no per-seat math for central staff or brand marketers.
The multi-brand D2C portfolio model itself keeps growing — PYMNTS has covered the rise of D2C holdcos and portcos since 2023 — and AI visibility is becoming one of the metrics groups standardize first, because it's new enough that no brand team has a legacy process to defend.
Frequently asked questions
Can different brands in the portfolio have different configurations?
Yes. Each brand gets its own dashboard, query bank, engine scope, approver list, and digest recipients. A grooming brand and a nutrition brand don't share a query universe, and the portfolio view rolls their scores up without flattening the source data.
Does the portfolio view aggregate SKUs across brands?
It aggregates scores, citation counts, and readiness metrics — not the SKUs themselves. Each brand's catalog stays its own. The central team sees which brands trend up or down and which PDP queues are overdue; brand teams keep their own detail views.
Can central HQ push PDP changes without brand-team approval?
Only if you configure it that way. Brand-team approval is the default before any write-back to a store. Central can be granted override rights for catalog-wide fixes — a schema migration, say — with an audit log every brand team can see.
How does pricing work for three or more brands?
The Agency & Enterprise tier prices per brand with portfolio discounts as the count grows, and no per-seat charge — central staff and brand marketers share the same contract. Contact sales for a quote against your exact portfolio.
What does central IT need to approve?
The usual list, and it's ready: SSO via Okta, Google, or Azure AD; a signed DPA on request; per-brand role scoping; and an audit log of every write to any store. eCommerce Insights processes catalog data only — titles, descriptions, schema, metafields — no customer PII.
Ask AI about eCommerce Insights for multi-brand portfolios
Have your preferred AI engine summarize this page for your group.
Retire the portfolio spreadsheet
One contract. Six brands. Six clean dashboards.
Agency & Enterprise tier pricing for portfolios. SSO, DPA, and per-brand isolation by default.
9,400 SKUs · 6 brands · 1 rollup