Currently website sends these events to GA/GTM platforms:

• registrationInit (When user clicks Send Code button)
• registrationConfirmationKey (When user enters confirmation key and clicks Verify button)
• registrationFinished (When user clicks Create Account button)
• login (When user logs in)
• logout (when user logs out)
• slipBuy (When user buys slip)
• addBetToBettingSlip (After adding bet to betting slip )
• depositSuccess (When user makes a successful deposit)
• withdrawalSuccess (When user makes a successful withdrawal)
• myAccountMenuDepositButtonClick (When user clicks deposit button. Different labels are sent for mobile and desktop buttons)

registrationInit

{
  // Data sent to GA
  action: 'registration_init',
  event_category: 'registration',
  
  // Data sent to GTM
  event: 'registrationInit',
  action: 'registration_init',
  category: 'registration',
}

registrationConfirmationKey

{
  // Data sent to GA
  action: 'confirmation_key',
  event_category: 'registration',
  
  // Data sent to GTM
  event: 'registrationConfirmationKey',
  action: 'confirmation_key',
  category: 'registration',
}

registrationFinished

{
  // Data sent to GA
  action: 'finished',
  event_category: 'registration',
  
  // Data sent to GTM
  event: 'registrationFinished',
  action: 'finished',
  category: 'registration',
}

login

{
  // Data sent to GA
  action: 'login',
  event_category: 'authorization',
  
  // Data sent to GTM
  event: 'login',
  action: 'login',
  category: 'authorization',
}

logout

{
  // Data sent to GA
  action: 'logout',
  event_category: 'authorization',
  
  // Data sent to GTM
  event: 'logout',
  action: 'logout',
  category: 'authorization',
}

slipBuy

{
  // Data sent to GA
  action: SLIP_TYPE,
  event_category: 'slip_buy',
  event_label: USER_ID,
  
  // Data sent to GTM
  event: 'slipBuy',
  action: SLIP_TYPE,
  category: 'slip_buy',
  label: USER_ID,
  eventUUIDS: EVENT_UUIDS,
  amount: AMOUNT,
  walletType: WALLET_TYPE;
}

SLIP_TYPE can be:
- 'fastbet' (when user is logged out)
- 'bet' (when user is logged in)

USER_ID can be:
- user id when the user is logged in
- 'null' when the user is logged out

EVENT_UUIDS is an array of event uuids, e.g. b78a17bc-17e9-52f8-b8d0-7db8ccdeda9d.
AMOUNT is total betting slip amount.
WALLET_TYPE is wallet type used when purchasing a slip - 'main', 'promo' or 'bonus'

addBetToBettingSlip

{
  // Data sent to GA
  action: 'addBetToBettingSlip',
  
  // Data sent to GTM
  action: 'addBetToBettingSlip',
  gameModuleName: GAME_MODULE_NAME,
  eventUUIDS: EVENT_UUIDS,
  market: MARKET,
  selection: SELECTED,
}

GAME_MODULE_NAME represents game module from the APP. For instance, 'prematch', 'keno', 'horses', etc...
EVENT_UUIDS is an array containing event uuids, e.g., '3ce479b2-31aa-56e5-945d-5e3da9d3d0e7'.
MARKET is bet market.
SELECTED is bet selection.

depositSuccess

{
  // Data sent to GA
  action: METHOD,
  event_category: 'deposit',
  event_label: USER_ID,
  value: AMOUNT,
  
  // Data sent to GTM
  event: 'depositSuccess',
  action: METHOD,
  category: 'deposit',
  label: USER_ID,
  value: AMOUNT,
}

METHOD is current users selected payment method, e.g. 'manual', 'retail', 'mlipa' and etc..
USER_ID is current user id
AMOUNT is user's deposit amount

withdrawalSuccess

{
  // Data sent to GA
  action: METHOD,
  event_category: 'withdrawal',
  event_label: USER_ID,
  value: AMOUNT,
  
  // Data sent to GTM
  event: 'withdrawalSuccess',
  action: METHOD,
  category: 'withdrawal',
  label: USER_ID,
  value: AMOUNT,
}

METHOD is current users selected payment method, e.g. 'manual', 'retail', 'mlipa' and etc..
USER_ID is current user id
AMOUNT is user's withdrawals amount

myAccountMenuDepositButtonClick

{
  // Data sent to GA
  action: 'click',
  event_category: 'deposit',
  event_label: LABEL,
  value: 1,
  
  // Data sent to GTM
  event: 'myAccountMenuDepositButtonClick',
  action: 'click',
  event_category: 'deposit',
  event_label: LABEL,
  value: 1,
}

LABEL can either be 'desktop-my-account-menu-deposit-button' or 'mobile-my-account-menu-deposit-button'