admin:online-platform-cms:google-events

This is an old revision of the document!


Google Analytics/Google Tag Manager events

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 (When successfully 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)

Events and their data:

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,
}

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

addBetToBettingSlip

{
  // Data sent to GA
  action: 'addBetToBettingSlip',
  
  // Data sent to GTM
  gameModuleName,
  eventUUIDS,
  market,
  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'
  • admin/online-platform-cms/google-events.1667495016.txt.gz
  • Last modified: 2022/11/03 17:03
  • by evaldas-luksys