Service model
Field playbooks
Repeatable sequences we use on application analytics engagements—so audits finish with artefacts, not a slide deck that expires.
-
Frame — one decision worth answering
We open with the decision that is stuck: a disputed funnel, a retention chart that moved after an SDK change, or a taxonomy nobody owns. Scope stays narrow on purpose.
-
Access — read-only where possible
You grant temporary read access to the analytics tool, event stream, and relevant docs. Audits do not require write rights to production schemas.
-
Inventory — make synonyms visible
Events, properties, funnel steps, and identity rules are listed before recommendations. Silent gaps surface here, not as a late-week surprise.
-
Prioritise — ship impact first
Fixes are ordered by how much they change decisions this quarter. Cosmetic renames wait behind broken step events and identity resets.
-
Handoff — artefacts you keep
You leave with written definitions, QA scripts, and a walkthrough. Ongoing operation only continues if you separately book Measurement Office Hours.
Ready to start?
Most teams begin with a Tracking Contract Workshop. If a single conversion path already argues with reality, tell us which path and we will suggest Conversion Path Instrumentation instead.