Blueprint playbook
Inventory first, rename second. Synonyms and voids are listed before any recommendation so product and engineering argue about the map—not about memory.
Service model
Engagement playbooks
Reusable sequences so audits and traces finish with artefacts your team can keep—not a slide deck that expires after the kickoff glow.
Path-trace playbook
One conversion path, real devices, live stream. Fixes are ranked by how much they change decisions you make this quarter.
Signal-study playbook
Timezone, identity, and SDK checklist before any retention story. Behaviours worth protecting come after the artefacts are ruled out.
Office-hours playbook
Upcoming instrumentation reviewed before it ships. Async taxonomy answers and a monthly pulse keep schemas from drifting between audits.
-
Intake — name the stuck decision
We start with one question: a disputed path, 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. We do not need write rights to your production schema for an audit.
-
Inventory — make the mess visible
Events, properties, path steps, and identity rules are listed before recommendations. Silent gaps show up here, not in a late-week surprise.
-
Repair plan — ranked by shipping impact
Nice-to-have renames wait behind broken step events and identity resets. You see the order before we write the final artefacts.
-
Handoff — artefacts your team owns
Written definitions, QA scripts, and a walkthrough. We do not keep operating your stack unless you separately book Measurement Office Hours.
Ready to request a playbook?
Most teams begin with a Product Event Blueprint. If a single conversion path is already arguing with reality, tell us which path and we will suggest a Conversion Path Trace instead.