Data warehouse

Definition
A data warehouse is one central place where a copy of business data from every system is combined so it can be queried together.

Why it matters

Each system knows only its own slice. The ad platform knows the click, the CRM knows the deal and the billing system knows how much the customer paid and for how long. A warehouse combines them, so the return by channel becomes something you calculate rather than guess.

It also lets you look back. Operational tools often show only the current state of a record, while a warehouse can keep history, so you can compare cohorts of customers from the same month and see how they behave over time.

It creates accountability as well. A team can see which campaigns and segments actually perform, and everyone reads the same numbers. The price is set-up, definitions and upkeep, so it pays when decisions need data from more than one system.

How to apply it

  • Start with the systems that hold your key decisions: the CRM, the marketing tool and billing.
  • Load raw data first and reshape it inside the warehouse, so remodelling later never means extracting again.
  • Agree what a customer, a sale and revenue mean before building reports. A managed warehouse can be set up in an afternoon, but those definitions take longer, and that is where an analytics engineer helps most.
  • Build a handful of shared reports instead of letting every team query it its own way.
  • Add a new source only once the current ones are trusted and used.

What it is

Business tools such as a CRM, a billing system and an ad platform are built to run daily operations, one record at a time. A data warehouse is built for the opposite job: reading large amounts of data to answer questions that cut across systems. Well-known examples are Google BigQuery, Snowflake and Amazon Redshift.

Data reaches the warehouse through a data pipeline, and it stays separate from the live tools, so a heavy report never slows down the CRM. The warehouse holds a copy. The original system stays the place where records are created.

Take the question "which channel brings customers who stay for more than a year?" The ad platform knows the click, the CRM knows the deal and the billing system knows how long the customer paid. In a warehouse that question becomes one query. Without it, someone matches names across three exports by hand.

Common mistakes

  • Buying a warehouse when a spreadsheet would still do. A few thousand rows from two tools rarely need one.
  • Treating it as a dumping ground with no definitions, so the same word means three things.
Worked example

Suppose a twelve-person agency wants to know which channel brings clients who stay more than a year. Ad spend sits in one platform, leads in the CRM and payments in the billing tool. Answering by hand means matching names across three exports, which takes most of a day and often gives up. The team loads a nightly copy of each source into Google BigQuery, where the tables join on a shared client ID. The question becomes one query. In this example, referrals keep clients for 16 months on average against nine months for paid search, so the agency moves part of its search budget into a referral scheme. The live CRM stays quick because the heavy queries run only on the copy.

Tools in the example

Some links are affiliate links: we may earn a commission at no cost to you. It never decides a ranking. How we work with partners

  1. Article

    Data modelling

    Turning what lands in a warehouse into trusted tables.

  2. Article

    ETL / ELT

    The two patterns data follows on its way in.

  3. Article

    Single Source of Truth

    The principle a warehouse helps to deliver.

  4. Article

    Single customer view

    Usually built by joining records inside a warehouse.

  5. Article

    Reverse ETL

    Sending warehouse results back to the tools a team uses.

Where it shows up

  • Measuring what works and following data to make better decisions. It tells you which changes are worth keeping and which to drop.
    22 chapters