Skip to main content

Overview

Here are the 3 core concepts you need to know:
  1. Events are the things that happen in your app.
  2. Users are the people who use your app.
  3. Properties are the attributes of your users and events.

1. Events

An event is a data point that represents an interaction between a user and your product. Events can be a wide range of interactions. For example, every time a user connects a wallet or performs an transaction on your app, there are details which describe that action the moment it happens. Actions like visiting a page, connecting a wallet, and depositing on a DeFi protocol can all be tracked as an event in Formo. The Formo SDK automatically captures and tracks page and wallet events. You can also track custom events and contract events.

2. Users

A user is the specific individual who completed an interaction with your product. Each user has a unique identifier that you can use to track their activity. Formo distinguishes between anonymous users and wallets:
  • Anonymous users aren’t tied to any wallets. All users starts as anonymous users until they connect a wallet.
  • Wallets are tied to a unique Ethereum or Solana address. When the user connect to these identities, their wallets are identified and tracked.
Wallets are automatically linked to the user when multiple wallets are connected in the same session. Linked addresses are visible in the wallet profile.

3. Properties

Properties are additional information about users and events.
  • Event properties are attributes that describe details specific to the particular instance of an event. For example, if you had a Purchase Completed event, you could specify what the user purchased, the total value of the order, and the payment method used.
  • User properties are traits describing the user and apply across all their future events until the properties are modified. Formo’s SDK captures several user properties by default, and you can also set up your own properties to track.
Properties examples:
  • A Connect Wallet event has wallet address and chain ID (Ethereum, Base, etc.)
  • A Page View event has page URL, referrer URL, and other metadata.
  • A User has net worth and first-touch UTM parameter properties.
When you track custom events, you can also set properties to describe the event. For example, if you had a Purchase Completed event, you could specify what the user purchased, the total value of the order, and the payment method used.