Interactive


BUSINESS INTELLIGENCE GAMING INNOVATION GROUP


GiG Logic: create your own rules


G3 interviews Mike Broughton, Director of Logic at Gaming Innovation Group, about the iGaming platform provider's flagship product, GiG Logic. He explains how the algorithm-based system bypasses the traditional development cycle, facilitates cross-selling and responsible gaming.


What is GiG Logic?


GiG Logic is a real-time, event-based scalable solution which essentially listens to what players are doing both offline and online. If a player spins a game or makes a deposit, it reacts in milliseconds to whatever that user is doing.


Mike Broughton, Director of Logic, Gaming Innovation Group


We put the emphasis on the savvy user rather than waiting for the standard development cycle of planning it out, giving it to developers, having it returned, and going through the testing cycle - this can take months before anything actually gets out the door. Logic gives you the ability to jump onto the system and write rules specific to your users so it is safe and sandboxed without potentially damaging anything.


P148 NEWSWIRE / INTERACTIVE / MARKET DATA


In itself, Logic is absorbing all of these messages (from player actions through to any API call) and following your flow logic. Te frontend then allows you to drag and drop like a flow chart, dragging rules and building blocks so you can build your logic within the messages.


For example, a player makes a deposit. Is it over £100? Is the lifetime deposit greater than £1000? Logic can then tag the player allowing the user to mark him as self-excluding or to undertake an appropriate form of responsible gaming action. Logic allows you to respond to the messages in the system in real-time. We have over 100 prefabricated building blocks you can play with and are processing around 52 million messages a day. Approximately, that is an overview of GiG Logic.


What was the rationale behind the creation of the algorithm-based system? Whose idea was GiG Logic and how long was the development process?


GiG Logic was born two and a half years ago from a frontend platform and the developers of the project could not cope with the challenging workload. So, they went and created some soft rules as they were known then. Back in my previous role I saw its potential as a product if we could top and tail it. For two years, we topped and tailed it.


How has GiG Logic performed since its launch earlier this year at ICE?


It is doing very well and we’re getting tremendous feedback from the demo’s. We’ve been building up a strong pipeline of opportunities with operators (land based as well as online) who are both looking at Logic as a stand alone as well as part of our wider platform offering. It has tremendous potential in its adoption, watch this space.


How does GiG Logic bypass the traditional development cycle?


We put the emphasis on the savvy user rather than waiting for the standard development cycle of planning it out, giving it to developers, having it returned, and going through the testing cycle - this can take months before anything actually gets out the door. Logic gives you the ability to jump onto the system and write rules specific to your users so it is safe and sandboxed without potentially damaging anything. You can ABC test it as much as you like.


We are putting the emphasis on user flow, responsible gaming and new technology, in addition to everything the product already has. You can create new user flows, experiences and bonuses, anything you want, into the system at whatever speed you want.


Why is a real-time rules engine preferable to using a developer or code?


Whilst you will still need to have code in the backend, Logic allows you to create rules on the fly. If you have a campaign coming up towards Christmas, you can say that if a user logs into the


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  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176