Regimen
← All work/Dental · Analytics & measurement
Case study

Perth Dental Group.


01 · KPI4 sites unifiedCross-site reporting on one dashboard
02 · KPIMonthly → weeklyCross-site spend allocation cadence
03 · KPI5th siteOnboarded into the schema without rework
01
The problem

The problem

A Perth dental group ran four sites across the metro corridor and could not answer simple questions about cross-site performance. Each site had its own GA4 property, its own consent banner, its own attribution model. The group's owner had three different agencies sending three different conflicting weekly reports.


02
The constraint

The constraint

Three different agencies sending three different weekly reports is a tooling problem most groups never solve — measurement in dental tends to be afterthought. Server-side instrumentation, OAIC-aligned consent management, and a single source of truth dashboard is engineering work, not reporting work. The harder constraint was schema-level: defining 'qualified consult' once across four sites so cross-site allocation held up to scrutiny.


03
The approach

The approach

One server-side GA4 implementation, one consent management plumbing, one attribution model agreed across all four sites. Reporting consolidated to a single Looker dashboard with definitions documented per metric. Compliance review done at the schema level, not at the dashboard level.


04
The outcome

The outcome

Cross-site reporting consolidated to one dashboard, three competing agency reports retired by month two. Decision lead time on cross-site spend allocation fell from monthly to weekly. The dashboard has absorbed a fifth-site acquisition into the schema without engineering work.