Multi-store
Five storefronts. One set of numbers.
Enable a unified brand view across multiple regional Shopify stores, built on a unified real-time database rather than five reports stitched together. Each store keeps its own store view, its own pixel and its own dashboard.
Any number of domains, currencies and ad accounts. Historical data is synced into the brand view.
Features
What the unified brand view gives you
One brand view on top, independent store views and tracking underneath.
Brand view
Brand-level totals
Orders, sessions, ad spend and contribution margin combine across every store view in real time, into one set of numbers.
Tracking
Pixels stay separate
Each domain keeps its own pixel and server-side event stream. No shared pixel, no cross-market contamination.
AI
One MCP endpoint
Ask about the whole brand or a single market in the same question, without switching accounts or exporting anything.
Drill-down
Back down to one store view
Every number in the brand view breaks apart again by store, market, campaign, creative and SKU. Nothing is lost on the way up.
Currency
One reporting currency
Orders land in local currency and convert at the rate on the order date, so brand totals reconcile to the books.
Architecture
One database, five tracking pixels
Most multi-store reporting is a stitching job: five separate databases, queried one by one, reconciled overnight into a spreadsheet that is already stale by the time anyone reads it. This is not that. Every store writes into the same real-time database from the same event pipeline.
A single real-time store
Every storefront writes into one database. The brand view is a scope on that data, not a federated query fanned out across five systems and merged afterwards.
Every pixel feeds both, at once
The same event lands in the store view and the brand view in the same instant. No nightly job, no sync window, no drift between the two.
Same freshness at every level
Whatever is true for a single market is true for the brand total at that moment. Open a store view and the brand view side by side and they agree.
Architecture
Why the pixels stay separate
Merging reporting is easy. Merging tracking is what breaks brands. BooleanMaths keeps the two apart: one brand view on top, independent data flows underneath, so gaining the brand view never costs you signal quality in any single market.
CAPI stays scoped per market
Each store's Conversion API feed goes to its own Meta and Google ad account. Event match quality per market is unaffected by the brand view sitting on top.
Privacy handled per region
GDPR for the UK and EU stores, DPDP for India, APP for Australia. Consent and retention rules apply per store rather than to one merged pool.
Reversible by design
If a store is sold, spun out or shut down, its data detaches cleanly. Local teams keep the store view they already work off.
How it works
Live in three steps
Step 1
Install on every store
Add the BooleanMaths app to each domain and connect the ad accounts behind it. Every store gets its own store view and its own pixel.
Step 2
Define the brand view
Point every store view at one brand view, or keep the originals standing and feed a separate parent alongside them. The second option stays reversible.
Step 3
Backfill and go live
Historical data from every store is migrated into the brand view, so prior periods report correctly from day one. Around three weeks end to end.
