Please enable JavaScript.

Coggle requires JavaScript to display documents.

Mixpanel events (Function specific (Mobile events https://docs.google…

- - - - One event can be triggered from different places (example: watchlist.remove).
        
        Testing activities
        
        Execute a trackable event from more than one places and check in Mixpanel if it's recorded more than once. [RRS(Here we can list the different evens that can be triggered from several parts of the system in a google sheet . Example https://docs.google.com/spreadsheets/d/1MNpAXE8H4p_URJBevLQhdoJUzNzSTvovBBeHUg8yCYw/edit#gid=0. This information would be very useful to have, so I can use to explore each journey from where the event can be triggered, so I can test if there are some events missed *
        
        Go through different flows in order to reach one event and check in Mixpanel if everything is recorded properly
  - - - Conversion rate between different events may be a lot lower than previous versions
        
        Testing activities
        
        Test if the chosen events have the expected conversion rate in the funnels after being recorded in the Live View on dev or staging
        
        Check and compare the conversion rate between two or three events in the different versions
        
        Test if the chosen events are showing in the Live View on the dev or staging environment
  - - - The events triggered by on person may be separated into different profiles
        
        Testing Activities
        
        Create a few accounts and trigger different events. Check in User Profile if everything is linked to the correct users
        
        Create an account on iOS and then log in with the same one on Android (and vice versa). Check if the recorded events are linked to one User Profile
      - Some user properties may be missing
        
        Testing Activities
        
        Check if all of the required fields are available in the existing User Profiles https://docs.google.com/spreadsheets/d/1GauITUlT9booWVhPm7NfY1NicF7-vnrGLclNSfsnvAY/edit?ts=5e611344#gid=1533311896
        
        Create a few accounts and check if all of the required fields in the users' profiles are present.
      - FTD time may be wrong
        
        Testing activities
        
        Create a few accounts and make deposits. Go to the User profile and check if the date and time is correct.
        
        Check if the event in Mixpanel Live View has the correct value for the property "IsFirst"
  - - - Incorrect naming of the properties
        
        Testing Activities
        
        Trigger some events that have 1 or more custom properties and double check them with the spreadsheet. https://docs.google.com/spreadsheets/d/18z2awXTvZGkT-qUMlYqoBA8VpHpaIN5SeEUGdD3dfoc/edit#gid=202440476
        
        Check in Mixpanel where does the problem come from: device/browser/version
      - Incorrect property values
        
        Testing Activities
        
        Try triggering the same event a few times, while changing the property (for example: searching different countries)
        
        Check where the problem comes from: browser/version/device
      - Properties not showing
        
        Testing Activities
        
        Trigger the same event a few times and check if the custom properties are showing
        
        Check the custom properties on different environments
        
        Check on different devices/browsers
- - - - Go thorough the same flow on the different platforms (web, ios and android) to detect where is the wrong naming is coming from *RRS: here is when we need to list in a sheet those flows, something like this https://docs.google.com/spreadsheets/d/1S1ADXUpoCxYYaiyRNqiVzOu5MGnuJ9yQU8zGnE_A2fQ/edit?usp=sharing
      - Check in previous versions of the apps/website if the naming is correct by going through the same flow
  - - - Check in the Funnel section if the selected events are for the same platform
      - Check if there was a conversion rate in the previous versions
      - Check the conversion rate in the different environments
  - - - Create a few accounts on iOS, go to the funnels and select two events - one from before the registration and one after. Filter the results to show only todays's events and only the used iOS version. The conversion rate should be > 0%
      - Create a few accounts on Android, go to the funnels and select two events - one from before the registration and one after. Filter the results to show only todays's events and only the used Android version. The conversion rate should be > 0%
      - Create a few accounts on the website, go to the funnels and select two events - one from before the registration and one after. Filter the results to show only todays's events. The conversion rate should be > 0%
  - - - Create a few accounts and trigger different events after that (the events should have the Mixpanel ID)
      - Trigger events after the Registration on different platforms and check if the events show in Mixpanel with the Mixpanel ID as a Distinct ID
- - - - Check on different devices the same events are recorded if the same flow is executed
      - History check: Check in Mixpanel what was being tracked, when there was a valid crash in the area of tracked events
  - - - Check in Insights the events that are being tracked
      - Check if all of the events are being tracked on different environments
      - Check if all of the events are being tracked on the different platforms
  - - - Stop the internet connection while sending the event
      - Check in Mixpanel if the event is sent
      - Check if the event is sent after the internet connection is restored
- - - - Check if after the maintenance mode the events during the time have been recorded
      - Check how the apps/website react when Mixpanel is under maintenance
  - - - Turn off the internet connection on the device and trigger an event immediately after that
      - Trigger an event and immediately turn off the internet connection
- - - - Check if the information sent to Mixpanel is private to the user
      - Check if the user has accepted the T&C before his private information is sent to Mixpanel
  - - - Check when a request is sent, if the token is also sent
      - Check in the Mixpanel properties for the different events in the Live view if there is a token field
      - Try triggering an event from Android, iOS and web and check if one or more of them is sending a token
- - - - Create an account on iOS/Android and log in with it in the website. The Distinct ID in Mixpanel should be for one and the same user.
      - Try logging events with one account while being on Android and iOS
      - Try logging events with one account while being on Android and web
      - Try logging events with one account while being on iOS and web
- - - - Testing activities
        
        Check if the PRs for the event is merged in prod (in that case, the events should be tracked in all of the environments)
        
        Test the same events on the different environments to check if one of them is problematic
        
        Test on the different platforms to check if there is a problem with one of them
    - - Testing activities
        
        Check if the events are recorded in the correct environments
        
        Check if the selected environment on the device is correct
- - - - Check in Mixpanel if the only event from the Registration process, containing the user's entered data is "Signup Successful"
      - Check if the data recorded before the T&C acceptance is not the users' private data
- - - - Trigger multiple events really quickly on Android. Go to Mixpanel and check in the Live view if everything is being recorded.
      - Trigger multiple events really quickly on iOS. Go to Mixpanel and check in the Live view if everything is being recorded.
      - Trigger multiple events really quickly on the website. Go to Mixpanel and check in the Live view if everything is being recorded.
- - - - Try sending the same event from different devices simultaneously and check in the Live View if the events are recorded and their data is correct