Your dbt tests passed. Why did the metric still move?
Wednesday, September 161:30 PM PT
Retention metrics often break in production due to inconsistent definitions, trial conversions, and account-level complexity. At Frame.io (Adobe), we saw the same metric product different results across Segment, Amplitude, and data warehouse models, leading to confusion across product, growth, and leadership teams.
In this talk, I'll show how we reframed retention as a modeling problem and used dbt to build a centralized, reliable metrics layer. We redesigned cohort and activity models, standardized metrics definitions, and implemented dbt test to catch inconsistencies early.
What attendees will learn:
- How retention metrics break in real production systems
- Common failure modes: cohort instability, activity definition, identity, and timing
- How to design stable cohort and retention models in dbt
- How to standardize metric definitions across teams and tools
- How to use dbt tests to enforce metric correctness and prevent drift
Check out more sessions
- Breakout session
From dbt Core to Fusion: How CarGurus unlocked dbt State and AI at scale
Jordan Morgan / CarGurusStephen Thibeault / dbt LabsView session - Breakout session
A practitioner's guide to federated dbt Mesh at scale with Data Project Factory
Trang Trinh / KrampView session - Breakout session
Open Data Infrastructure in practice: unlock your dbt projects with Apache Iceberg and mesh
Jack Lowery / FivetranAnna Lee / dbt LabsView session
