Once we have a way to quantify usage, we can compare usage between variants of an app.
To do this, we need to log an event when someone enters an experiment variant. I’ve heard this referred to as an “impression” or “activation” event. Firebase ABT simplifies things a bit by enabling developers to identify an existing event for this purpose. The basic idea is to serialize events by time, identify a common start point (the activation event), and then compare the events after for things like increased signups, or increased time using the app, increased purchases, etc.
It’s critical this event is logged equivalently for all variants so we can compare apples to apples. This is an example of where QA features in analytics SDKs and services is helpful.
Testing identical variants (“A/A testing”) is helpful for identifying issues in analysis infrastructure.
As with analytics, building experimentation infrastructure is non-trivial and the cost of errors is high, so using an existing provider is advisable.