Write the instrumentation blueprint before the sprint starts
Event names invented mid-coding rarely survive the next rename of the same screen.
When tracking is treated as a ticket at the end of a sprint, engineers invent labels under time pressure. The same action appears as submit_form, form_complete, and checkout_tap across platforms. Reports become archaeology.
Prefer verbs that describe user intent, not UI chrome. Keep platform out of the event name; put it in a property so web and app stay comparable. Document allowed properties on the same day the name is created.
An Instrumentation Blueprint engagement spends the first sessions only on the map—because until the map exists, every later fix guesses at the wrong root.