Concepts
Background material on architecture, design decisions, and Meridian integration boundaries.
Pages
- Why meridian-tools exists — Google Meridian is the modelling engine.
meridian-toolsis the workflow layer around that engine. It makes a Meridian modelling project easier to review, rerun, compare, hand over, and refresh without forking or modifying Meridian. - Adoption brief for agency teams — This page is the short version for teams deciding whether to use
meridian-toolsaround Google Meridian. - Architecture —
meridian-toolsis a companion package designed for agency teams that use Google Meridian as their client-facing MMM (Marketing Mix Modelling) engine. It provides a stricter, more reproducible workflow around Meridian without forking the upstream library. - Design decisions — This document records the key design decisions in
meridian-toolsand the reasoning behind them. It is intended for maintainers and contributors who need to understand why things are built the way they are. - Meridian integration — This document describes how
meridian-toolsintegrates with Google Meridian, the boundaries of that integration, and the risks associated with different coupling levels.