Integrate additional events into google analytics query into the prototype

[annatekl]

Context

The goal is to implement event tracking for user interactions on the Vortex PMF prototype using Google Tag Manager (GTM) and Google Analytics. The provided code template listens for specific user actions (like clicks) and pushes events to the GTM dataLayer. These events will help track user behavior for analysis in Google Analytics. We are still missing 3 events (listed in the requirements) for funnel monitoring.

Code template to create and push events to the data layer for the specified list of events was provided:

document.getElementByID("ID").addEventListener('click', function(){
    dataLayer.push({
      'event': 'eventName', //such as select_vault_manually
      'label': 'vaultID', // use actual vaultID
  });
})

Please refer to the ticket

Requirements

• [ ] Add below type of events to the data layer:
• Change network to Polygon prompt
• Connected wallet address

[annatekl]

Hey team! Please add your planning poker estimate with Zenhub @b-yap @bogdanS98 @ebma @gianfra-t @TorstenStueber

[ebma]

I don't really understand this ticket, can you please flesh out the requirements and context a bit more @annatekl? I assume this is supposed to build on prior work done in relation to Google Analytics but then I don't understand the content of the 'context' section.

[annatekl]

changed the title and the context a bit @ebma, let me know if the context is still unclear

[prayagd]

@annatekl is this good to have ticket?

[ebma]

Okay, the context is clearer now but the requirements are not.

• Change network to Polygon prompt

I guess this means you want to have an event sent when a user changes the network in his wallet to polygon. Why does this even matter? They need to

• Value input before wallet connect

Here you want to have the value the user input before connecting the wallet?

• Value input after wallet connect

And here after connecting?

Why is any of these three events important? Wouldn't it be enough to know the amount that the user entered before starting the KYC? And why are we interested in the event related to Polygon? So we know if Polygon is a dealbreaker for some users?

[annatekl]

I guess this means you want to have an event sent when a user changes the network in his wallet to polygon. Why does this even matter? They need to

We want to see what networks are used the most, if they often switch polygon, it means that our users are on another network where we should offer the offramp

[annatekl]

• Value input before wallet connect

Here you want to have the value the user input before connecting the wallet? We are interested to see the amount expectation from the user, that can different from the actual amount, thats for looking into the volumes user is interested in

• Value input after wallet connect

And here after connecting? amount that user is typing after wallet connect can mean that user didn't have the amount in his wallet. but also significant percentage of users who modify the amount downward, may indicate that they are encountering unexpected fees. Why is any of these three events important? Wouldn't it be enough to know the amount that the user entered before starting the KYC? And why are we interested in the event related to Polygon? So we know if Polygon is a dealbreaker for some users? If users frequently lower the amount after wallet connection, it could mean that there’s something causing them to scale back, which wouldn’t be captured by just looking at the pre-KYC amount.

[prayagd]

@vadaynujra should we merge this and #198 ticket?

[vadaynujra]

@prayagd @ebma from the events requested in this ticket, the ones yet to be implemented are:

• Connected wallet address
• Prompt for changing network

Shall we update this ticket to only include these two and make it ready?

[ebma]

Yes, please do.

[prayagd]

Shall we update this ticket to only include these two and make it ready?

Had added the first, the second is already there