Change Details

{F2566672}

{F2566672} Build an A/B/C (3-condition) test to test: 1. The default experience ("test-group-a") 2. The search box from the first A/B test ("test-group-b") 3. The search box from the first test, plus typeahead improvements ("test-group-c") The logic for admitting people to the test: 1. 1 in 200 people get into the overall schema 2. Of these, 1 in 10 get into the test. The remaining 9/10 get the default experience and are not in a test group - they are for dashboarding 3. Of the 1 in 10, 1/3rd of users are distributed to each test group. We should keep the same client technical requirements that the default eventlogging has, unless doing so would damage the quality of the data. In that case, we should keep those same technical requirements for the non-tested (9/10) group. If that's not possible, let me know.

{F2566672} Build an A/B/C (3-condition) test to test: 1. The default experience ("test-group-a") 2. The search box from the first A/B test ("test-group-b") 3. The search box from the first test, plus typeahead improvements ("test-group-c") The logic for admitting people to the test: 1. 1 in 200 people get into the overall schema 2. Of these, 1 in 10 get into the test. The remaining 9/10 get the default experience and are not in a test group - they are for dashboarding 3. Of the 1 in 10, 1/3rd of users are distributed to each test group. We should keep the same client technical requirements that the default eventlogging has, unless doing so would damage the quality of the data. In that case, we should keep those same technical requirements for the non-tested (9/10) group. If that's not possible, let me know.