website

twitter

Infrastructure

Helio

# Helio Average revenue per user (ARPU) Methodology

## 1. Overview

Average Revenue Per User (ARPU) measures the average daily revenue generated per active user on the Heliopay protocol. This metric divides the total daily revenue by the number of daily active users to understand the monetization efficiency of the platform. ARPU helps assess user value and revenue generation patterns by calculating how much revenue each active user contributes on average per day.

## 2. Data sources

The ARPU calculation relies on the following raw blockchain data sources:

- **Solana native transfers**: Native SOL transfer events from Solana blockchain where tokens are sent to Heliopay fee collection addresses
- **Solana SPL token transfers**: SPL token transfer events from Solana blockchain where tokens are transferred to Heliopay fee collection addresses  
- **End-of-day token price feeds**: Daily closing prices for all tokens to enable USD conversion
- **Token metadata**: Token contract information including decimal precision for accurate amount calculations
- **Transaction data**: Solana transaction records containing signer information to identify users

## 3. Step-by-step calculation

### Component A: SOL fee collection
- **Purpose**: Captures native SOL fees paid to Heliopay protocol
- **Logic**: Identifies all Solana native transfers where the recipient is the Heliopay fee account `FudPMePeNqmnjMX19zEKDfGXpbp6HAdW6ZGprB5gYRTZ` and the sender is not the same fee account (to exclude self-transfers). Records the transaction timestamp, signer address, and transfer amount for each fee payment.
- **Key fields**: `block_timestamp` for timing, `transaction_signer` for user identification, `amount` for fee value, and hardcoded `token_address` as SOL identifier

### Component B: SPL token fee collection  
- **Purpose**: Captures SPL token fees paid to Heliopay protocol
- **Logic**: Identifies all Solana SPL token transfers where the recipient owner is the Heliopay fee account `FudPMePeNqmnjMX19zEKDfGXpbp6HAdW6ZGprB5gYRTZ` and the transaction signer is not the same fee account. Records the transaction timestamp, signer address, token contract address, and transfer amount for each fee payment.
- **Key fields**: `block_timestamp` for timing, `transaction_signer` for user identification, `token_address` for token type, `amount` for fee value

### Component C: Revenue aggregation
- **Purpose**: Combines and standardizes all fee data into USD-denominated daily revenue
- **Logic**: Unions SOL and SPL token fees, then groups by day and token address to sum total fees. Applies decimal correction based on token metadata and converts all amounts to USD using end-of-day price feeds. Aggregates across all tokens to produce total daily revenue in USD.
- **Key fields**: `timestamp` truncated to daily boundaries, `fees` summed and converted to USD

### Component D: Daily active user calculation
- **Purpose**: Counts unique users who paid fees each day
- **Logic**: Combines transaction signers from both SOL and SPL fee transactions, then counts distinct users per day using HyperLogLog algorithm. Groups users by timestamp and removes duplicates to identify unique daily active users. Uses efficient probabilistic counting for scalability across multiple dimensions.
- **Key fields**: `user_dau` containing unique user addresses, `timestamp` for daily grouping

### Component E: User aggregation across dimensions
- **Purpose**: Provides DAU counts at different breakdown levels
- **Logic**: Uses HyperLogLog to aggregate daily active users across four dimensions: project-level (total), chain-level (by blockchain), user-type-level (by role), and product-level (by product). Merges HyperLogLog sketches and extracts final counts for each dimension while maintaining user uniqueness.
- **Key fields**: `user_dau` as final distinct count, `dimensions` indicating aggregation level

### Final aggregation
- **Combining components**: Revenue and DAU data are joined by date using the calculate_arpu macro, which performs the division operation while handling cases where DAU might be zero or null
- **Currency conversion**: All revenue is converted to USD using end-of-day price feeds with proper decimal adjustments based on token metadata
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with consistent daily grouping across all components
- **Final calculation**: ARPU equals daily revenue in USD divided by daily active users, with the finalize_metric_arpu macro applying schema validation and gap-filling strategy to ensure continuous time series with zeros for missing days

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

Helio

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape