Level 2. The platform runs the campaigns. The warehouse remembers everything.
At some point your questions outgrow the platform UI: joining customer data with margin, comparing cohorts across years, feeding a model. The answer is a triangle: tracking flows into Bloomreach Marketing (Engagement), raw data flows onward into BigQuery or another warehouse, and computed results flow back for activation.
Three corners, each doing what it’s best at.
Each corner does one job. Events flow in, the full history lands in the warehouse, and the results flow back into your campaigns.
Level 2 · Platform + warehouse
Tracking (site and app SDKs)
Events in real time
Bloomreach Marketing
AI
Raw events out, scores and audiences back
Data warehouse
AI
Tracking.
Your site and apps send events to Bloomreach through its SDKs.
Bloomreach Marketing (Engagement).
Profiles, segmentation, real-time triggers, and campaign execution.
The warehouse.
Raw event data from Bloomreach joins your orders, margin, logistics, and offline data.
The return path.
Computed attributes, scores, and audiences flow back into Bloomreach as imports, where campaigns and personalization act on them.
An example.
Finance asks which customers were profitable last year once returns and shipping are counted. Bloomreach has the purchases. The warehouse adds margin, returns, and logistics, and computes a profit score per customer. The score flows back into Bloomreach, so next week’s campaign treats a profitable customer differently from one who costs money.
Board-level reporting, cost control, and data science, all in one place.
Board-level reporting.
Marketing data joined with finance data, in the BI tool the company already uses.
Cost control.
Full history in the warehouse at warehouse prices, not platform prices.
Data science.
Churn scores, LTV models, and propensities computed on raw data, then activated through campaigns.
AI context.
The full, joined history AI needs, where a language model can answer plain-language questions across all your data.
One version of the truth.
The warehouse is the referee when platform numbers and finance numbers disagree.
The export pipeline, the warehouse model, and the return path.
We build the export pipeline, the warehouse model on the receiving end, the return-path imports, and the monitoring that tells you when any leg of the triangle stalls. We also set the governance: which system owns which attribute, so the triangle doesn’t turn into two databases that disagree. We work with your data engineers, or do the pipeline work ourselves on BigQuery setups.
A warehouse with no consumer is a standing cost.
If nobody in the company writes SQL and reporting needs fit the platform UI, the warehouse is a standing cost with no consumer. Stay at level one; revisit when the first analyst is hired. And if multiple departments beyond marketing need the customer data asset, look at level three instead.
Questions your platform UI can’t answer?
Book a discovery call. Bring one of those questions. We’ll sketch the triangle that answers it. A co-founder leads your project.