gray-crayon-3459206/13/2023, 8:15 AM
helpful-application-710706/13/2023, 8:33 AM
set to the cluster ID rather than the default
. with some cluster ID so that randomization is consistent within cluster, but also track the user ID as an attribute with the trackingCallback
2. Then just analyze metrics at the user level (to be honest I am not 100% certain this will work, but I believe it should as the tracking callbacks from step one should still have the user id as well). Of course, the main issue here is that your uncertainty will likely be greatly underestimated and the statistics we produce will be largely invalid.
Ideally between the two (in terms of statistical power) would be official support for cluster randomization and while on our radar, is not high priority right now.
gray-crayon-3459206/13/2023, 8:40 AM
helpful-application-710706/13/2023, 8:44 AM
gray-crayon-3459206/13/2023, 8:47 AM
helpful-application-710706/13/2023, 8:47 AM