search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
What we're seeing is that operators really care about the


first-time deposit flow. Tat's the most common thing they want tested. We'll then have testers sign up for an account and deposit, recording the number of seconds it took in


total, how many fields it had, what the payment options where, and how seamless the overall FTD process was.


KYLE WILTSHIRE CEO TESTA


and share feedback on if the appropriate markets are there. We are building out this massive community of people from all over the globe who are capable of testing gambling sites who bring unique skillsets to the table.


Are testers always geographically bound?


I would say 70 - 80 per cent of test requests are geographically bound. Sometimes clients just care about a particular product, and it doesn't matter, but often implying our services is about targeting a certain region. In the US, for example, there's extreme challenges with testing and getting visibility in that market because there's so many stringent regulations around geo-compliance.


You can't even sign up or view the sites unless you're physically in the market. Getting visibility of what the actual experience looks like for a sports bettor in Illinois is difficult when your people are based in Sweden or Malta.


Are testers ever assigned based on their demographic?


Yep, so there's kind of a middle layer and that's where the magic happens. Tere are instances where a customer would tell us who we'd like to test a product with. From there, we can assign who those testers will be and what experience we want them to have. Te testers then execute it, and the important thing is that we validate all the work in between.


As we've built this business, I've been surprised at how many operators and providers at scale have been managing this problem


themselves for years. Sometimes they have in-house testers and it's quite sophisticated with entire departments and teams that manage them. Other times it's just they have friends and family being spammed constantly to see if SMS works in this or that market.


At TESTA, we assign all the information to a tester, get the result, verify if the result was proper, then put this information into a format the customer can understand. We manage the data and the information as it goes down to the ground to be tested and then back to the provider.


What are operators and providers testing for?


What we're seeing is that operators really care about the first-time deposit flow. Tat's the most common thing they want tested. We'll then have testers sign up for an account and deposit, recording the number of seconds it took in total, how many fields it had, what the payment options where, and how seamless the overall FTD process was. Providers investigate game performance quite a lot. Tat's a measure that, as you get farther and farther out from their area of expertise or home markets, they get quite curious about.


For example, should our spin time or load time be different? Tis is what it is in the European market, but should it be like that in Asia or Latin America? For providers that are in 30-plus markets, they're interested to get feedback from the ground. Aside from the first-time deposit flow, operators are keen to test big changes so common examples are if a platform is being updated, a new feature is being added to the sportsbook or before committed significant marketing spend before a major promotion.


79


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142