Tracking

Contracts (On-chain)

All Gnosis Safe contract state and interactions on-chain can be analyzed via Dune analytics. This includes properties such as:

• Number of Safes deployed
• Safe version
• Number of owners and threshold
• Number of transactions made
• Fund store
• ...

Gnosis Safe dashboards on Dune are tagged with the label Gnosis Safe. There is a main dashboard and a long list of dashboards for all kinds of purposes.

Web (Off-chain)

General

• Google analytics is used for tracking.
  • Mainnet
  • Rinkeby
  • xDai
  • EWC
  • Volta
• Default properties such as device types and operating system are tracked.
  • e.g. Number of unique visitors daily/weekly/monthly or time spent on page
• The landing page is tracked separate from the app:
  • Landing page
  • Landing page (Rinkeby)
• Users have to accept the analytics cookie before they show up in the tracking. We don't track users that don't accept.

Custom events

• Wallet connected
  • category: 'Wallets'
  • action: 'Connect a wallet'
  • label: <provider name>
• Safe created
  • category: 'User'
  • action: 'Created a safe'
  • value: <safe address>
• Navigation (category: Safe Navigation)
  • Open Safe list via Sidebar (action: Safe List Sidebar)
  • Open coins (action: Coins)
  • Open collectibles (action: Collectibles)
  • Open transactions (action: Transactions)
  • Open address book (action: AddressBook)
  • Open Safe apps (action: Apps)
    • label: <Safe app name>
  • Open settings (action: Settings)
    • Details (label: Details)
    • Owners (label: Owners)
    • Advanced (label: Advanced)

Misc

• Download counts of the desktop app can be found here: https://githubstats0.firebaseapp.com/
• The Safe transaction service has an endpoint (/multisig-transactions/analytics/) to provide data on the number of Safe app transactions based on the origin field.

Mobile (Off-chain)

General

• Firebase analytics is used.
• Data is synced to Google analytics
  • Production Mainnet
  • Production Rinkeby
  • Staging
• Default user properties are tracked.
• Personalized advertising features are disabled
• How to check tracking events with BigQuery

Custom user properties

Docs

User properties should be tracked with every single event.

num_safes

• Integer (Tracked as String though since Firebase only allows Strings for user properties.)
• Should be the number of Safes that the user has added on their device.
• Number is 0 after fresh install
• Number is increased when adding a Safe to the device
• Number is decreased when removing a Safe from the device.

push_info

• string
• unknown if we haven't asked for push access yet (iOS only since we have push permission on Android by default)
• enabled if we have push notification permission (or enabled it after previously denying)
• disabled if the user denied push permission (or removed it after previously allowing)

num_keys_imported

• Integer (Tracked as String though since Firebase only allows Strings for user properties.)
• Should be the number of imported owner keys.

Screen view tracking

• Every screen should be tracked as separate event.
• We cannot use the Firebase native screen tracking since that's not working for us on iOS with SwiftUI. There is an issue on Github for this.
• The screen name is set as event name with a screen_ prefix. Overview screen tracking
• There is a limit of 500 unique event names on Firebase, afterwards they get dropped (Error code 8)
• There are some reserved names we cannot use.