Analytics for Solana Apps: What to Track and How

Key Takeaways
Analytics for a Solana app has to join three views that usually live in separate tools: the web visit, the wallet connection, and the transaction.
Web analytics tools do not know what a wallet is. Chain data does not know where a user came from. The value is in the join.
The core metrics are visitors, wallet connect rate, transaction success rate, active wallets, retention, and volume or revenue per channel.
Solana differs from EVM in ways that affect tracking: wallets connect through Wallet Standard, a transaction is a set of instructions, and failed and rejected transactions are common enough to measure.
Start with automatic capture of wallet events, add two or three custom events for your key actions, and build one funnel from visit to first transaction.
Analytics for Solana apps means measuring the whole path of a user: the visit to your site, the wallet connection, and the transactions that follow. Web analytics tools cover the first step and nothing after it, because they do not know what a wallet is. Chain data covers the last step and nothing before it, because it does not know where a wallet came from. A Solana team needs both, joined on the wallet.
This guide covers which metrics to track, what is different about Solana, how wallet events are captured, and how to get started.
Why Is Web Analytics Not Enough for a Solana App?
A web analytics tool counts sessions and page views. It stops at the moment that matters most for a Solana app: the user connects a wallet and signs a transaction.
Question | Web analytics | Chain data | Analytics built for onchain apps |
|---|---|---|---|
How many people visited? | Yes | No | Yes |
Which campaign brought them? | Yes | No | Yes |
How many connected a wallet? | No | No | Yes |
How many completed a transaction? | No | Yes | Yes |
Which campaign brought the wallets that transact? | No | No | Yes |
What else do my users hold and do? | No | Partly | Yes |
The fifth row is the one teams ask about most. It needs the visit and the transaction in the same record.
What Should a Solana App Track?
Track the steps between a visit and a repeat transaction, and the drop between each pair of steps.
Metric | What it tells you |
|---|---|
Visitors | Reach of your site and campaigns |
Wallet connect rate | Share of visitors who connect a wallet. A low rate points to the landing page or the connect flow |
Transaction start rate | Share of connected wallets that start a transaction |
Transaction success rate | Share of started transactions that confirm. Rejections and failures are separate causes |
Active wallets | Wallets that performed a meaningful action in a period |
Retention | Share of wallets that come back after 1, 7, and 30 days |
Volume and revenue | Value of the activity, in total and per wallet |
Volume and revenue per channel | Which sources bring wallets that produce value, not only clicks |
Why transaction outcomes deserve their own metric
A transaction on Solana can end in several ways, and each one has a different fix.
Outcome | What happened | What to look at |
|---|---|---|
Rejected | The user declined in the wallet | The prompt, the timing, the fee shown |
Failed or reverted | The transaction was sent and did not succeed | Slippage settings, account state, program errors |
Broadcast but not confirmed | Sent, with no confirmation recorded | Network conditions, priority fees |
Confirmed | Success | Your baseline |
A team that tracks only confirmed transactions cannot see the first three, and those are where most of the lost conversions are.
What Is Different About Solana?
Four things affect how you track a Solana app.
Wallet Standard. Solana wallets register with the page through Wallet Standard. An analytics SDK can observe connections and disconnections through it, without wrapping wallet methods and without depending on which wallet library your app uses.
Clusters. A Solana app talks to a cluster: mainnet, devnet, or testnet. Analytics has to know which one, or test activity mixes with real activity.
Instructions, not single calls. One Solana transaction can contain several instructions for several programs. "The user did a swap" is something your app knows and should name in a custom event. It is not always clear from the transaction alone.
A different address format. A Solana address is case-sensitive and is not the same format as an EVM address. A user with a Solana wallet and an EVM wallet has two addresses that nothing onchain links.
How Are Wallet Events Captured on Solana?
There are two levels, and which one you get depends on how your app is built.
Your app uses | Captured automatically | Needs explicit tracking |
|---|---|---|
Any Wallet Standard integration, including Solana Kit and wallet-adapter | Wallet detection, connect, disconnect | Transactions and signatures |
framework-kit, with its store passed to the SDK | The above, plus cluster switches and the lifecycle of transactions that the store records: started, broadcast, confirmed, reverted, rejected | Transactions sent through hooks that do not write to the store |
Custom events fill the rest. Name the actions that define your product, such as a swap, a deposit, a mint, or a stake, and send one event for each with the properties you care about: the pair, the amount, the value.
How Do You Attribute Solana Transactions to Marketing?
Attribution joins the first visit of a user to what their wallet does later.
Capture the source on the first visit. UTM parameters, the referrer, and referral codes.
Keep it with the visitor. An anonymous ID in the browser carries the source until the wallet connects.
Attach it to the wallet at connect. From that moment, every event of that wallet has a source.
Report by outcome, not by click. Compare channels by wallets that transact, by volume, and by retention.
The fourth step changes decisions. A channel that brings many visitors and few transacting wallets looks good in a web analytics tool and bad in this report.
What Can You Learn About Solana Users Beyond Events?
Events tell you what a wallet did in your app. The wallet's public history tells you who it is.
Wallet profiles. Token balances and net worth for each Solana wallet. On Solana, profiles show token holdings. DeFi positions are available for EVM chains.
Segments. Group wallets by what they hold, how active they are, or where they came from.
Lifecycle. New, returning, power user, at risk, churned, and resurrected, based on each wallet's activity in your app.
Linked wallets. Wallets that one person or team controls, found through shared identity and through a shared funding address. See how to detect sybil wallets on Solana.
How Do You Get Started?
Install the SDK and set the cluster. For a Solana-only app, turn off EVM tracking.
Check automatic capture. Connect a wallet and confirm that the connect event arrives.
Add custom events for two or three key actions. Start with the one action that defines an active user.
Build one funnel. Visit, wallet connect, first transaction.
Add campaign parameters to your links. Then compare channels by the last step of the funnel.
Review weekly. Look at the largest drop in the funnel first.
See Install and the Solana integration guide in the docs, and supported chains for what is available on Solana.
Frequently Asked Questions
What is analytics for Solana apps?
It is the measurement of a user's whole path in a Solana app: the visit, the wallet connection, and the transactions. It joins web data and wallet data on the wallet address, so that a team can see which sources bring wallets that transact.
Can Google Analytics track a Solana app?
It can track visits and page views. It cannot see wallet connections, transactions, or what a wallet holds, so it cannot answer which campaign brought the users who transact.
What metrics matter most for a Solana app?
Wallet connect rate, transaction success rate, active wallets, retention, and volume or revenue per channel. Together they show where users drop off between a visit and a repeat transaction.
How are Solana wallet connections tracked?
Through Wallet Standard. Wallets register with the page, and an SDK can observe connections and disconnections without wrapping wallet methods. This works with Solana Kit, wallet-adapter, and other Wallet Standard integrations.
Do I need to track transactions manually on Solana?
It depends on your stack. With framework-kit and its store passed to the SDK, the lifecycle of transactions recorded in the store is captured. Transactions sent through hooks that do not write to the store, and signatures, need an explicit tracking call.
How is Solana analytics different from EVM analytics?
Wallets connect through Wallet Standard, apps target a cluster, one transaction can hold several instructions, and addresses have a different format. The metrics are the same. The capture is different.



