Part 3 · 1 chapters · ~8 min
Instrumenting What You Ship
Success criteria written before building, an event taxonomy and naming, tracking plans reviewed with code, server-side versus client-side events, privacy in analytics, dashboards for a launch, and checking that the data is right before trusting it.
7
Measure in the same PR
code
tracking plan: clearance letter (reviewed with the PR) event properties fires when letter_entry_viewed source (home | loan_detail | push) the letter screen opens letter_eligibility_checked eligible (bool), reason the eligibility API returns letter_generated loan_type, duration_ms the PDF is ready (server-side) letter_downloaded method (download | share | email) the user saves or shares letter_verified verifier_country a receiving party opens the QR page (server-side) success criteria (written before building) - 60% of eligible users who open the screen generate a letter - p95 generation under 60 s - manual letter tickets down 50% after 6 weeks
| practice | why |
|---|---|
| server-side events for business facts (generated, paid, verified) | ad blockers and flaky networks do not lose them |
| client events for interaction (viewed, tapped) | only the client knows |
| no personal data in analytics properties | privacy law and trust (Disciplines course part 8) |
| verify events in staging before launch | broken tracking discovered after launch means no data for the decision |