Four data sources gathered into one dashboardAn email marketing agency running a portfolio of DTC brands
Four sourcesof client data in one dashboard the agency owns, and its clients can see.
- 3Brands, each an isolated tenant with its own login
- DailyEvery connector pulling into one shared schema
- One per storePurpose built commerce app, so the authorisation never expires
- Plain EnglishHow the conversion agent gets asked a question
The challenge.
The story only existed once somebody assembled it.
An email marketing agency reports to its DTC clients every month, and the numbers that matter live in four places that do not talk to each other. The email platform. The commerce platform. Web analytics. Product analytics. Each with its own definitions and its own export.
So the same picture gets rebuilt by hand, every month, out of four exports. Email performance here, revenue there, site behaviour in a third place, on site product behaviour in a fourth.
And when a client asks the obvious question, which flow actually drove revenue last month, answering it means opening four tabs and doing the joining in your head.
If that shape looks familiar, the consultation is where we go and find yours.
Start with the free consultationWhat we built.
One reporting layer, branded to the agency, on the agency's own accounts.
The dashboard carries their name and not ours, and it runs on their infrastructure throughout. What gets built is theirs to keep rather than something they rent back.
Underneath it, a multi tenant data layer with per tenant isolation and per client logins. Each brand sees only its own numbers. The agency sees across the portfolio.
Connectors pull all four sources on a daily sync into one shared schema, with derived metrics and aggregation on top, so a question about email and revenue together is one query instead of two exports and a spreadsheet.
Commerce authorisation is where systems like this usually break quietly. Standard credentials are barred for stores an agency does not own, and the expedient workaround expires and needs re authorising every week, which is how a dashboard dies. So every store got its own purpose built application, with its own connect and callback route, producing authorisation that does not expire.
On top of the data sits a conversion agent. Ask it about the funnel in plain English and it queries the warehouse rather than a summary of the warehouse. The email, commerce and analytics tools sit alongside the product analytics query tool as capabilities it can reach for, so its answer comes from the same numbers the dashboard is drawing.
The results.
Three client brands run as isolated tenants, each with its own login.
Four sources per brand feed one view, on a daily sync, in one schema.
The authorisation problem is solved rather than deferred: one application per store, and nothing to re authorise on a Monday morning.
What the agent changes is who gets to ask. A question about last month's flows no longer needs the one person who knows which export to run.
And the whole system sits on the agency's own accounts, so the reporting layer they put in front of their clients is a thing they own.
Tell us what yours looks like.
Bring us the part of your business that runs on someone remembering. We will tell you what it would take to build it out.