busy-horse-7382407/08/2022, 9:52 AM
event, which has
fields. If we're testing whether a content change helps people progress further, we might want to see whether more people make it to the end of the course, or to the next chapter, or whatever.
Currently we have to make an individual metric for every single thing we might want to look at. It'd be better if we could have a base
metric, maybe with some minimal initial filtering, then optionally filter on extra fields
Or as a rough equivalent, defining a metric with specific parameters which have to be filled in when selecting it (not as powerful, but maybe more compatible with e.g. SQL-backed metrics)