Anyone have any great tips or templates for defining product analytics events and properties e.g. in Amplitude?
I’m working on defining how we’ll instrument a flow from scratch (our first analytics instrumentation effort), and it is painfully hard to work through Amplitude’s implementation worksheet.
Bonus points if anyone knows of a great tool for annotating screenshots or designs with events and properties as opposed to working with a massive spreadsheet.
this series is super helpful on the ‘deciding what to measure’ part:
and if you use Figma, the team just released this plugin:
Imo best approach is to make a list of all the questions you’ll have “Eg what % of users make it past each step”, then ask an engineer how much effort it will take to implement the logging for each one, and then prioritize them based on effort vs impact, and let the engineer figure out how to instrument the event calls
I totally agree with that philosophy, and I’ve personally had success with that approach working with teams with more established product analytics.
This particular case is such a bear because we’re instrumenting one sliver of an existing app for the first time. We don’t have prioritization/trade-off decisions to make at this stage, as actual implementation effort is pretty light. The cognitive load right now is really more in the data architecture/engineering.
So either my brain will be melting or an Engineer’s brain will be melting. 
This topic was automatically closed after 180 days. New replies are no longer allowed.