Skip to main content
The Activity page shows a real-time view into what users are doing on your app. You can also track custom events and contract events.
Product Analytics Activity

Every event, as it happens.

Every event includes full properties and is captured without sampling.

​
Filter by event properties

Filter the activity feed by event properties to focus on specific user actions or behaviors.
Product Analytics Activity

Filter by any property to understand what users are doing.

Use filters to narrow events by any property to investigate a specific user journey or troubleshoot an issue.

​
How to use the activity feed

This section covers using the Activity Feed for investigation and user research.

​
Step 1: Open the Activity Feed

1

Go to the Formo Dashboard

Open app.formo.so.
2

Select your project

3

Click Activity in the left navigation

You’ll see a chronological stream of all events on your app.

​
Step 2: Understand event types

Each event has a structured schema and type based on the event specs: Click any event to expand and see all properties.
Product Analytics Event Properties

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:
1

Click Filter

2

Choose a property to filter by

3

Set the condition and value

Common filter combinations:
Activity Filters

Filter by any property to focus your investigation.

​
Step 4: Investigate a user’s journey

To see everything a specific user did:
1

Find any event from that user

2

Click the wallet address

3

View their complete Wallet Profile

See Wallet Profiles for more details.
Wallet Profile Activity Feed

View a user's activity feed.

Or search the Activity Feed directly:
1

Use the search box

2

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:
1

Filter by type = transaction

2

Look for the rejected status icon, or search by the user's address

3

Click to expand and see error details

4

Check the preceding events for context

Investigating a drop-off:
1

Search by the user's address

2

Look at their event sequence

3

Identify where they stopped (last event before leaving)

4

Check for errors or unusual patterns

5

Use Funnels to measure drop-off rates at each step

See Funnels for more details.
Investigating a flow issue:
1

Filter by a specific page

2

Look at what users do after visiting that page

3

Identify unexpected patterns

4

Use Flows to visualize common paths users take

See Flows for more details.

​
Common investigation patterns

“Why are users bouncing from our swap page?”
1

Filter: page = /swap

2

Look at events that follow page views

3

Count how many lead to connect vs. leaving

4

Check for errors or unusual device/browser patterns

“Which transactions are failing?”
1

Filter: type = transaction

2

Look for rejected transactions and expand each to review error details

3

Identify the most common failure reasons

4

Check if failures correlate with specific flows

“What do our best users do differently?”
1

Identify a power user from the Users list

2

Search Activity by their address

3

Study their event sequence

4

Compare to average user patterns

“Is our new feature being used?”
1

Filter by your custom event or page

2

See adoption over time

3

Check which user segments are using it

4

Look at the referrer to see how users find it