The activity feed shows you what users are doing in real-time.
Filter by event properties
Filter the activity feed by event properties to focus on specific user actions or behaviors.
Filter by any property to understand what users are doing.
How to use the activity feed
The Activity Feed is your real-time view into what users are doing on your app. This guide shows you how to use it for investigation and user research.Step 1: Open the Activity Feed
Go to the Formo Dashboard
Select your project
Click Activity in the left navigation
Step 2: Understand event types
Each event has a structured schema and type based on the event specs:| Event Type | What it captures |
|---|---|
page | Page view with URL path |
connect | Wallet connection |
disconnect | Wallet disconnection |
signature | Message signing |
transaction | Onchain transaction |
track | Custom events |
decoded_log | Smart contract events |
Each event has full properties and metadata available for deeper analysis.
Step 3: Filter to find specific events
Use filters to narrow down the feed:Click Filter
Choose a property to filter by
Set the condition and value
| Goal | Filters |
|---|---|
| Connects from Twitter | type = connect, referrer contains twitter |
| Visitors from marketing campaign | utm_source = newsletter |
| Events from mobile devices | device = mobile |
| Failed transactions | type = transaction, status = failed |
| Wallet connects from Twitter | type = connect, referrer contains twitter |
| Specific user’s activity | address = 0x… |
| Events on a specific page | path = /swap |
| High-value transactions | type = transaction, value > 1000 |
Filter by any property to focus your investigation.
Step 4: Investigate a user’s journey
To see everything a specific user did:Find any event from that user
Click the wallet address
View their complete Wallet Profile
View a user's activity feed.
Add filter: address = [wallet address]
See all events from this user in chronological order
Step 5: Investigate issues
When users report problems, use the Activity Feed to investigate: Investigating a failed transaction:Filter by type = transaction and status = failed
Find the user's transaction
Click to expand and see error details
Check the preceding events for context
Filter by the user's address
Look at their event sequence
Identify where they stopped (last event before leaving)
Check for errors or unusual patterns
Use Funnels to measure drop-off rates at each step
Filter by a specific page path
Look at what users do after visiting that page
Identify unexpected patterns
Use Flows to visualize common paths users take
Common investigation patterns
“Why are users bouncing from our swap page?”Filter: path = /swap
Look at events that follow page views
Count how many lead to connect vs. leaving
Check for errors or unusual device/browser patterns
Filter: type = transaction, status = failed
Group by error message or contract
Identify the most common failure reasons
Check if failures correlate with specific flows
Identify a power user from the Users list
Filter Activity by their address
Study their event sequence
Compare to average user patterns
Filter by your custom event or page path
See adoption over time
Check which user segments are using it
Look at the referrer to see how users find it