What is Event Tracking? Event tracking is the practice of recording specific user actions, such as clicks, signups, wallet connects, and transactions, as structured events with properties, forming the foundation of behavioral analytics.
Event Tracking Explained Think of a security camera log that notes every meaningful thing that happens in a building: who came in, which doors they opened, and when they left.
Event tracking is that log for a digital product. Every meaningful action a user takes is recorded as an event with a name, a timestamp, and properties that add context.
In Web3, events span both worlds: offchain events like pageviews and button clicks, and onchain events like wallet connects, signatures, and transactions. Stitched together by wallet address, they tell the full story of a user's journey.
What Event Tracking Means For Audience
Use Case
Product and analytics teams
Define and track the events that matter, then build funnels, retention cohorts, and dashboards on top of them
Developers
Instrument apps with SDKs to capture standard and custom events with structured properties
Growth teams
Use event data to measure activation, conversion, and the behaviors that predict retention
Examples A Web3 app automatically tracks pageviews, wallet connects, chain switches, signatures, and transactions after installing an analytics SDK.
A product team defines a custom event for completed swaps with properties for token pair and amount, enabling volume breakdowns by feature.
An analyst builds a funnel from a landing page event to a wallet connect event to a transaction event to find the biggest drop-off.
A developer sends backend events from a server SDK to capture actions that never touch the frontend.
FAQs What is an event in analytics? A structured record of a user action, with a name, timestamp, user identifier, and optional properties that describe the context of the action.
What are event properties? Key-value pairs attached to an event that add detail, such as the button clicked, the token swapped, the amount, or the campaign that brought the user.
What is the difference between auto-tracked and custom events? Auto-tracked events are captured by the SDK without extra code, such as pageviews and wallet connects. Custom events are defined by the team for product-specific actions like completing a quest.
Which events are unique to Web3 products? Wallet connects and disconnects, chain switches, message signatures, and onchain transactions, all tied to a wallet address rather than a cookie.
Why do event naming conventions matter? Consistent names and properties keep data clean and queryable. Inconsistent naming fragments the same action into multiple events and breaks funnels and reports.