admin:online-platform-cms:google-events

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
admin:online-platform-cms:google-events [2022/11/03 17:13] – [Events and their data:] evaldas-luksysadmin:online-platform-cms:google-events [2023/12/11 14:10] evaldas-luksys
Line 13: Line 13:
   * **withdrawalSuccess** (//When user makes a successful withdrawal//)   * **withdrawalSuccess** (//When user makes a successful withdrawal//)
   * **myAccountMenuDepositButtonClick** (//When user clicks deposit button. Different labels are sent for mobile and desktop buttons//)   * **myAccountMenuDepositButtonClick** (//When user clicks deposit button. Different labels are sent for mobile and desktop buttons//)
 +  * **viewContent** (//When the user visits Live/Prematch/Outright single event//)
  
-====== Events and their data: ======+====== Events and their data (GA): ======
  
 **registrationInit** **registrationInit**
 <code> <code>
 { {
-  // Data sent to GA 
   action: 'registration_init',   action: 'registration_init',
   event_category: 'registration',   event_category: 'registration',
-   +
-  // Data sent to GTM+</code> 
 + 
 +**registrationConfirmationKey** 
 +<code> 
 +{ 
 +  action: 'confirmation_key', 
 +  event_category: 'registration', 
 +
 +</code> 
 +**registrationFinished** 
 +<code> 
 +
 +  action: 'finished', 
 +  event_category: 'registration', 
 +
 +</code> 
 +**login** 
 +<code> 
 +
 +  action: 'login', 
 +  event_category: 'authorization', 
 +
 +</code> 
 +**logout** 
 +<code> 
 +
 +  action: 'logout', 
 +  event_category: 'authorization', 
 +
 +</code> 
 +**slipBuy** 
 +<code> 
 +
 +  action: SLIP_TYPE, 
 +  event_category: 'slip_buy', 
 +  event_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 
 +</code> 
 + 
 +**addBetToBettingSlip** 
 +<code> 
 +
 +  action: 'addBetToBettingSlip', 
 +
 +</code> 
 +**depositSuccess** 
 +<code> 
 +
 +  action: METHOD, 
 +  event_category: 'deposit', 
 +  event_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 
 +</code> 
 + 
 +**withdrawalSuccess** 
 +<code> 
 +
 +  action: METHOD, 
 +  event_category: 'withdrawal', 
 +  event_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 
 +</code> 
 + 
 +**myAccountMenuDepositButtonClick** 
 +<code> 
 +
 +  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' 
 +</code> 
 + 
 +**viewContent** 
 +<code> 
 +
 +  action: 'viewContent', 
 +  event_label: CONTENT NAME, 
 +
 + 
 +CONTENT NAME is event name. 
 +</code> 
 + 
 +====== Events and their data (GTM): ====== 
 + 
 +**registrationInit** 
 +<code> 
 +{
   event: 'registrationInit',   event: 'registrationInit',
   action: 'registration_init',   action: 'registration_init',
Line 33: Line 140:
 <code> <code>
 { {
-  // Data sent to GA 
-  action: 'confirmation_key', 
-  event_category: 'registration', 
-   
-  // Data sent to GTM 
   event: 'registrationConfirmationKey',   event: 'registrationConfirmationKey',
   action: 'confirmation_key',   action: 'confirmation_key',
Line 43: Line 145:
 } }
 </code> </code>
 +
 **registrationFinished** **registrationFinished**
 <code> <code>
 { {
-  // Data sent to GA 
-  action: 'finished', 
-  event_category: 'registration', 
-   
-  // Data sent to GTM 
   event: 'registrationFinished',   event: 'registrationFinished',
   action: 'finished',   action: 'finished',
   category: 'registration',   category: 'registration',
 +  userID: USER_ID
 } }
 +
 +USER_ID is current user id
 </code> </code>
 +
 **login** **login**
 <code> <code>
 { {
-  // Data sent to GA 
-  action: 'login', 
-  event_category: 'authorization', 
-   
-  // Data sent to GTM 
   event: 'login',   event: 'login',
   action: 'login',   action: 'login',
Line 69: Line 166:
 } }
 </code> </code>
 +
 **logout** **logout**
 <code> <code>
 { {
-  // Data sent to GA 
-  action: 'logout', 
-  event_category: 'authorization', 
-   
-  // Data sent to GTM 
   event: 'logout',   event: 'logout',
   action: 'logout',   action: 'logout',
Line 82: Line 175:
 } }
 </code> </code>
 +
 **slipBuy** **slipBuy**
 <code> <code>
 { {
-  // Data sent to GA 
-  action: SLIP_TYPE, 
-  event_category: 'slip_buy', 
-  event_label: USER_ID, 
-   
-  // Data sent to GTM 
   event: 'slipBuy',   event: 'slipBuy',
   action: SLIP_TYPE,   action: SLIP_TYPE,
   category: 'slip_buy',   category: 'slip_buy',
   label: USER_ID,   label: USER_ID,
 +  eventUUIDS: EVENT_UUIDS,
 +  amount: AMOUNT,
 +  walletType: WALLET_TYPE;
 } }
  
Line 104: Line 195:
 - user id when the user is logged in - user id when the user is logged in
 - 'null' when the user is logged out - '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'
 </code> </code>
  
Line 109: Line 204:
 <code> <code>
 { {
-  // Data sent to GA 
-  action: 'addBetToBettingSlip', 
-   
-  // Data sent to GTM 
   action: 'addBetToBettingSlip',   action: 'addBetToBettingSlip',
   gameModuleName: GAME_MODULE_NAME,   gameModuleName: GAME_MODULE_NAME,
Line 126: Line 217:
  
 </code> </code>
 +
 **depositSuccess** **depositSuccess**
 <code> <code>
 { {
-  // Data sent to GA 
-  action: METHOD, 
-  event_category: 'deposit', 
-  event_label: USER_ID, 
-  value: AMOUNT, 
-   
-  // Data sent to GTM 
   event: 'depositSuccess',   event: 'depositSuccess',
   action: METHOD,   action: METHOD,
Line 147: Line 232:
 AMOUNT is user's deposit amount AMOUNT is user's deposit amount
 </code> </code>
 +
 **withdrawalSuccess** **withdrawalSuccess**
 <code> <code>
 { {
-  // Data sent to GA 
-  action: METHOD, 
-  event_category: 'withdrawal', 
-  event_label: USER_ID, 
-  value: AMOUNT, 
-   
-  // Data sent to GTM 
   event: 'withdrawalSuccess',   event: 'withdrawalSuccess',
   action: METHOD,   action: METHOD,
Line 172: Line 251:
 <code> <code>
 { {
-  // Data sent to GA 
-  action: 'click', 
-  event_category: 'deposit', 
-  event_label: LABEL, 
-  value: 1, 
-   
-  // Data sent to GTM 
   event: 'myAccountMenuDepositButtonClick',   event: 'myAccountMenuDepositButtonClick',
   action: 'click',   action: 'click',
Line 187: Line 259:
  
 LABEL can either be 'desktop-my-account-menu-deposit-button' or 'mobile-my-account-menu-deposit-button' LABEL can either be 'desktop-my-account-menu-deposit-button' or 'mobile-my-account-menu-deposit-button'
 +</code>
 +
 +**viewContent**
 +<code>
 +{
 +   event: 'viewContent',
 +   action: 'viewContent',
 +   label: CONTENT NAME,
 +   eventUUIDS: [CONTENT ID],
 +   contentName: CONTENT NAME,
 +}
 +
 +CONTENT NAME is event name.
 +CONTENT ID is event uuid.
 </code> </code>
  • admin/online-platform-cms/google-events.txt
  • Last modified: 2024/05/09 06:34
  • by evaldas-luksys