Product Analytics Instrumentation

A tracking plan the whole team trusts: questions first, one naming convention, clear identity and consent rules, verified events on every platform and weekly checks that catch broken tracking early.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Product Analytics Instrumentation, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

207

Starter tasks

🧩 Product Management

Product Analytics Instrumentation

Defining and implementing the events and properties a product needs to track, so usage questions can be answered without guessing.

  1. Inventory of product questions the data must answer
  2. Audit of events the product already sends
  3. Event naming convention for the whole product
  4. Tracking plan as the single source of truth
  5. Choosing a product analytics tool
  6. User identity and anonymous ID strategy
  7. Owners and decision rights for tracking
  8. Separate analytics projects for development and production
  9. Consent and privacy rules for tracking
  10. First release of core lifecycle events
  11. Tracking spec in every ticket's definition of done
  12. Weekly event volume anomaly check
  13. Monthly tracking plan review
  14. Intake process for new tracking requests
  15. Analytics QA checklist for every release
  16. Quarterly data quality scorecard
  17. Schema change log for analysts
  18. Quarterly pruning of unused events
  19. Data dictionary for everyone who queries events
  20. Event volume and analytics cost budget
  21. Event data model basics for events, users and groups
  22. Funnel and cohort query fundamentals
  23. SQL on raw event tables in the warehouse
  24. Debugging events with SDK and network tools
  25. Time zones, sessions and timestamps
  26. Tracker blockers, bots and missing data
  27. Mobile SDK batching, offline queues and app versions
  28. Client-side versus server-side tracking decision
  29. Typed tracking code generated from the plan
  30. Schema validation at ingestion
  31. Customer data platform or direct SDKs
  32. Warehouse sync of product events
  33. Account-level analytics for business products
  34. Autocapture versus explicit events
  35. Recovering from a tracking gap
  36. Merging duplicate and inconsistent events
  37. Launch-day instrumentation readiness
  38. Analytics tool migration cutover
  39. Tracking plan sign-off workshop
  40. Annual analytics stack review
  41. Instrumentation fix day for the tracking backlog
  42. Lean tracking for a small team without an analyst
  43. Engineer onboarding to the tracking codebase
  44. Product manager inheriting an instrumented product
  45. Tracking across app versions in the wild
  46. Combining tracking after merging two products
  47. Personal data minimisation for sensitive products
  48. Data contracts between engineering and analytics
  49. Reconciling analytics with billing and backend records
  50. Cross-device identity stitching at scale

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Inventory of product questions the data must answer

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Before anyone names an event, the team needs the list of questions it expects analytics to answer: which plans convert, where new users stall, which settings large accounts change.

First tasks

  • Ask five colleagues for the three usage questions they most want answered
  • Rewrite each question to name the user, the action and the time window
  • Note beside every question the decision its answer would change
  • Rank the questions and agree the top ten with the product lead
  • Revisit the question list against what the team is now deciding @recurring(quarterly)

Audit of events the product already sends

Most products already emit dozens or hundreds of events from old SDK calls, autocapture and long-finished experiments, and nobody is sure which ones are trustworthy. An audit listing every event, its volume, where in the code it fires and whether anyone queries it gives an honest starting point for the tracking plan and shows what can be deleted.

First tasks

  • Export the full event list with 30-day volumes from the analytics tool
  • Search the codebase for every tracking call and map it to an event name
  • Flag events with near-identical names or meanings
  • Mark each event keep, fix, merge or retire with a one-line reason

Event naming convention for the whole product

Signed Up, signup_completed and user-registered living in the same project turn every query into a guessing game. One agreed convention, such as object then past-tense action in a single casing, plus rules for property names and values, lets a new engineer name an event correctly without asking and lets an analyst find it by searching.

First tasks

  • Collect twenty current event names as examples of what to fix
  • Choose the casing, word order and tense for event names
  • Write rules for property names, units and allowed values
  • Publish the convention and link it from the contribution guide

Make it yours.

Install Product Analytics Instrumentation, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.