Client stories
What teams noticed after assessments, activity reviews, and measurement design — including the awkward parts.
“The assessment showed our mobile checkout and web checkout were counting different payment states. We spent two weeks arguing about conversion before that became obvious.”
“I wished we had involved backend earlier — a few queue events were missing from the brief. Still, the final map made ownership clear enough that our next release shipped with matching counts.”
“The activity review was blunt about our double-fire on the password-reset flow. Fixing that alone cleaned up the weekly support report.”
“Quarterly health checks catch drift after each major release. Not glamorous work, but our board pack no longer needs a footnote explaining why mobile dipped.”
Case note: marketplace checkout reconciliation
A regional marketplace asked us to explain a persistent gap between mobile and web completion rates. The Connected Analytics Assessment found that web counted “payment intent created” while mobile counted “payment captured,” and that a retry path on web fired a second intent event.
We delivered a shared definition keyed to capture from the payment service, plus a short list of client-side fixes. Within one release cycle the weekly packs stopped needing a verbal disclaimer. The remaining work — tagging failed retries separately — stayed on their backlog by choice.
Case note: education platform health checks
An education product with frequent release trains booked quarterly Analytics Health Checks. Early sessions caught silent events after a navigation redesign; later ones focused on teacher-facing surfaces that had never been instrumented to the same standard as student flows.
The scorecards are short on purpose. Each check ends with tickets their engineers can schedule without another workshop.