UX Casino redesign
analytics-515 -516
test method
fake control group
test A/B
casino users vs. rest
casino live users vs. test casino users
live casino and casino will need to be tested separately
test in new tab
mobi vs web vs iO app vs Andr app
high level aim:
justify value of UX changes
notes
markets should be analysed separately
plan
general > specific
first: pick better version
target: pick better version
what means better
higher satisfaction from chosen game
willingness to spend more £
easier to pick a game
lower BR on games
longer time in game
or
more rounds
*account value when
started and ended game
higher avg. players days
in general
higher bets
higher NGR and avg. NGR
timing
test A/B
min. until significance
fake control group
min. 2 x avg. players days on casino
number of users significance
next if necessary: verification of smaller changes
UX horse betting changes
analytics-510
test method
fake control group
mobi vs web vs iO app vs Andr app
test A/B
high level aim:
justify value of UX changes
primary target: verify if change
increased bets value and margin
willingness to face higher risk
higher NGR and avg. NGR
notes
markets should be analysed separately
higher bets on horses market
timing
test A/B
min. until significance
fake control group
min. 2 x avg. players days on casino
number of users significance
shorter time on listing
do we have user segmentation by risk attitude?
split by tier
split by bets value segment
users who were displayed modified page vs. rest of horse racing pages' users
why?
higher number of horse bets
why?
more efficient
avg. page load time
smaller number of errors
split by platform
add tracking for clicked game position