[Event Tracking] Add mixpanel event tracking

[lmcmz]

https://app.gitbook.com/o/btnrCjBfFA1CijnAHf9d/s/uD5IIQEzBNOcwceEz9qr/

[tombeckenham]

List of events and items to do:

• super_events
• Identify User
• script_error
• delegation_created
• on_ramp_clicked
• coa_creation
• security_tool
• multi_backup_created
• multi_backup_creation_failed
• cadence_transaction_signed
• evm_transaction_signed
• ft_transfer
• nft_transfer
• Transaction Result
• account_created
• account_creation_time (time it takes to create an account)
• account_recovered

[tombeckenham]

I've had a look at the Mixpanel documentation to remember how security works and whether we'll have issues with tracking in the chrome extension. In short, yes we will:

1. The project token is not secret - it can be used and embedded freely and it is not locked to any domain. This is the way Mixpanel was designed. This does mean that anyone can access that project token and use it to send data to our Mixpanel. But why would they... ?
2. However, mixpanel-browser front end SDK can only be used in the popup. It cannot be called from the service worker. This is because the SDK requires access to the window object - which service workers can't get to. There is no option for service workers besides creating a backend proxy service
3. If I do move all the tracking to the popup, we'll get issues with ad blockers. Mixpanel's documentation suggests that up to 30% of all events will be lost. With our user base, potentially that number will be higher. I'm wondering, however, if that would be a good thing? It would give our users a way to disable mixpanel tracking if they want to stay anonymous. If we move tracking to the backend, we'd need to create a feature to disable it and include code to disable it

My recommendation is that I implement Mixpanel tracking on the front end.

• Our users can block tracking using standard means if they want to
• It's less complicated to implement. I won't have to create a backend, or batch api calls etc
• It'll give us "some information" quickly

I'm also thinking that maybe we want to put in some sort of transaction analytics that reads the flow blockchain and sends information to mixpanel. That would be a better "backend" way to track what users are doing.

[Peppermint1020]

List of events and items to do:

• super_events
• Identify User
• script_error
• delegation_created
• on_ramp_clicked
• coa_creation
• security_tool: not applied on extension
• multi_backup_created: not applied on extension
• multi_backup_creation_failed: not applied on extension
• cadence_transaction_signed
• evm_transaction_signed
• ft_transfer
• nft_transfer
• Transaction Result
• account_created
• account_creation_time (time it takes to create an account)
• account_recovered

[Peppermint1020]

Tested on https://github.com/Outblock/FRW-Extension/actions/runs/12092593566
(1) All event names are currently displayed as "page view"; they should display the event names from the GitBook events.

Expectation behaviour is:

(2)We have Production Mixpanel project Id. Please spilt our DEV and Production ENV accordingly.

[Peppermint1020]

@tombeckenham
Please check following issues.
Tested on https://github.com/Outblock/FRW-Extension/actions/runs/12345848657

• super_events

We need include following keys for all events

• Identify User

• script_error:This event has not been triggered as not meet script error.
• delegation_created

• on_ramp_clicked

• coa_creation
  This event has not been triggered when I create COA account for previous account. https://www.flowscan.io/tx/6f4cf74ae0866cdb0097d526b7ba88d7e9a84e07b0df49ecd17ff91bab18d508
• cadence_transaction_signed
  This event has not been triggered when send ft/nft from flow to other flow address.
• evm_transaction_signed
  This event has not been triggered when have evm transaction
• ft_transfer

The value of type is type of FT send and ft_identifier should in following format

• nft_transfer

The nft_identifier should in following format.

• Transaction Result
  This event has not been triggered.
• account_created

We miss key_type.

• account_creation_time (time it takes to create an account)
  This event has not been triggered
• account_recovered
  The "method" field is empty.

[Peppermint1020]

Confirm with Tom.
The issue is the MixPanel transaction tracking code is repeated across dozens of components that we are planning to refactor.
We decide to go with what we have with MixPanel then update it later