Guide · See the gold layer

See the gold layer.

Raw source data is refined into clean, business-ready tables by a dbt medallion pipeline. Your dashboards and Aurelia Auto read the top layer — gold — directly.

Bronze → silver → gold

After a source lands (see Connect your sources), dbt models refine it through three layers, each building on the one before:

LayerWhat it holdsPurpose
BronzeRaw source data, as landedA faithful copy of what each connector replicated — nothing dropped.
SilverTyped, conformed, de-duplicatedConsistent types, keys and grain across sources; duplicates and noise removed.
GoldDashboard martsBusiness-ready tables shaped for a specific decision surface.

The gold marts

The gold marts live in the warehouse gold schema. Each one powers a dashboard view and is available to Aurelia Auto through the semantic layer.

MartContents
gold.dailyDaily channel performance — spend, reported revenue, orders and new customers.
gold.salesSales by region and category — revenue, contribution margin and orders.
gold.channelChannel incrementality — MMM incremental revenue and each channel’s modelled share.
gold.cohortAcquisition cohorts and predicted lifetime value.
gold.dim_metaDataset metadata — date bounds and filter members. Not governed.

Who reads gold

These surfaces read the gold marts directly, so everyone works from the same numbers:

  • Profitability — revenue, contribution and incrementality.
  • Customer LTV — acquisition economics, value and payback.
  • Total commerce — owned and marketplace demand in one view.
  • Customer 360 — unified identities, lifecycle segments and source coverage.
  • Aurelia Auto — reads the same channel-performance marts through the semantic layer to explain results and draft budget moves.

How it’s built & isolated

In production, Airbyte lands raw data, dbt builds each layer, and the marts export into your workspace’s namespace. Gold tables are tenant-keyed — every row carries a tenant_id, and a workspace only ever reads its own rows. A shared gold table that isn’t tenant-keyed is never served.

Until a source has synced and the dbt build has completed, a workspace has no gold data yet — dashboards show an empty state, and a demo workspace shows representative sample data instead.