Do you need a marketing data warehouse, or just a dashboard?
The honest answer is that most mid-market marketers do not need one yet. Here is how to tell whether you do.
A dashboard is sufficient when reporting reads from one platform and history beyond that platform's retention does not matter. A marketing data warehouse earns its cost under four conditions: cross-platform questions, retention beyond platform limits, per-location rollups, and numbers that must be reproducible and auditable. For most mid-market marketing datasets, running costs are tens of dollars a month; connector licensing is usually the larger line.
The short answer
If your reporting reads from one platform, and losing history past that platform's retention window would not hurt, a dashboard is enough. Build the dashboard and stop.
A warehouse earns its cost when at least one of four things is true: you need cross-platform questions answered, you need history beyond platform retention, you need per-location rollups on consistent definitions, or you need numbers that can be reproduced and audited later.
Everything below is about telling which situation you are in, because the cost of guessing wrong in either direction is real.
What a warehouse actually is
A marketing data warehouse consolidates ad platform, analytics, call tracking and CRM data into one queryable store — normally BigQuery — with scheduled ingestion and a semantic layer.
A semantic layer is the set of versioned definitions, in SQL, in one place, that turn raw platform data into the metrics you report. It exists so a metric name means exactly one thing regardless of which dashboard displays it.
That definition is the part people skip, and it is the part that produces most of the value. Two dashboards calculating "cost per lead" slightly differently is not a technology problem; it is a definitions problem, and the warehouse is where definitions get to live once.
Three options, honestly compared
| Manual exports | Connector → dashboard | Warehouse | |
|---|---|---|---|
| Setup cost | None | Low | Project |
| Monthly effort | Days | Low | Low |
| History | Whatever you saved | Platform limits | Unlimited |
| Cross-platform joins | By hand | Limited | Native |
| Auditability | None | Weak | Full lineage |
| Right for | One-off analysis | Single-source reporting | Multi-source, multi-location, finance-grade |
The Monthly effort row is where manual exports lose. Someone spends the first week of every month pulling, aligning and reconciling spreadsheets, and that cost never appears as a line item because it is absorbed by salaried time.
The Auditability row is where the CFO conversation happens. If a figure is questioned six months later and you cannot reproduce it from source data, the number was never really evidence.
What it costs to run
For most mid-market marketing datasets, BigQuery storage and query costs are modest — commonly tens of dollars a month rather than thousands — provided tables are partitioned and scheduled queries are bounded.
Cost overruns almost always come from unpartitioned tables scanned by scheduled queries several times a day. Partitioning, clustering, bounded queries and a monthly budget alert are set at build time, not after the first surprising invoice.
Connector licensing, not compute, is usually the larger line. Managed connectors are worth their licence where the source is genuinely complex; where a platform API or a scheduled export does the job, that is what should be built. Connector choice is design work, not an afterthought.
The infrastructure should be billed to your own cloud project directly. If a provider marks up your cloud spend, that is a conflict of interest sitting on top of your data.
The argument that persuades a CFO
Marketing leads are usually persuaded by capability — the questions they could finally answer. Finance is usually persuaded by durability.
Platform retention windows expire. Connectors change formats. Agencies get replaced. A warehouse in your own cloud project means the historical record survives all three, and the transformation that produced any figure is in version control.
That is also what makes the reporting layer replaceable. When the semantic model is the contract, Looker Studio, Tableau or Power BI become a display choice you can reverse rather than a platform you are married to.
Where to start
Not with the warehouse. Start by writing down the four definitions of your primary conversion that already exist across the ad platform, analytics, call tracking and your CRM. Most organisations have never seen them side by side, and the exercise sometimes resolves the problem without building anything.
If the numbers disagree in ways nobody can explain, that is a conversion attribution audit first — a warehouse built on unreconciled definitions just centralises the confusion.
If they agree and you still cannot answer cross-platform questions, that is when a marketing data warehouse is the right build. Scope it on source count and location count, and get a monthly cost estimate before anyone provisions anything.