In-Game Analytics

Helika in-game analytics covers users, engagement, retention, and revenue. We enrich it with web3 data to drive deeper analysis into user behavior and product optimization. Some of the metrics included are: DAU, session length, cumulative play time, sessions per day, d1 - d30 retention, ARPU, ARPPU, etc. (see Metrics & Controls)

Value

⭐ Understand player retention across various wallet segments to identify strategies that enhance engagement.

⭐ Evaluate the effectiveness of your game’s monetization rate across various wallet segments.

⭐ Explore the on-chain spending habits of your players based on their geographic locations.

⭐ Correlate your game's popularity and frequency of player interactions with on-chain transaction data.

Use Cases

Analyze player retention by combining on-chain NFT transactions with in-game retention data, revealing strategies to enhance engagement across wallet segments.

Correlate on-chain NFT transactions with off-chain in-game spending data to identify high-value wallet segments, enabling precise monetization strategy adjustments for enhanced monetization rates.

Overlay historical on-chain transactional data with off-chain player engagement data to tailor marketing campaigns to specific demographics and wallet segments.

Merge on-chain and off-chain metrics to identify peak activity times, player engagement trends, and factors influencing session lengths for various wallet segments.

LiveOps

Helika's LiveOps product helps studios find the patterns that engage desired player behavior and create incentives to drive those outcomes. With LiveOps, studios can refine event ideation and motivate users to engage with events in a given meta of the games that distribute rewards but also maintain engagement and drive monetization.

Value

⭐ LiveOps relates to modifying game configuration files to maximize retention and profitability. Developers are typically manipulating the backend settings and parameters of a game in real-time without deploying a full update. This practice allows game studios to test, iterate, and optimize various elements to enhance player experience and monetization.

⭐ By leveraging LiveOps in this manner, game developers can be more agile and responsive to their player base. Instead of waiting for major updates to make changes, they can fine-tune the game experience in real-time, which can lead to improved player satisfaction, retention, and monetization.

Use Cases

Dynamic Tuning: Developers can adjust game parameters on-the-fly based on real-time data. For instance, they might tweak the difficulty level, spawn rates of items, or rewards given to players based on player behavior and feedback.

Monetization Adjustments: Developers can experiment with the pricing of in-game items, offer special deals, or introduce new items temporarily to see how players respond. Adjusting these parameters can help optimize the game's profitability.

Personalization: Based on player data, developers can personalize the gaming experience. For example, players who haven't made an in-game purchase might be offered a special one-time deal, while frequent spenders might receive exclusive offers or content.

Feedback Loop: By collecting and analyzing player data continuously, developers can understand the impact of the changes made through the config files and adjust their strategies accordingly.

Use Cases

Drive Desired Player Behavior: Find the patterns that engage desired player behavior and create incentives to drive those outcomes. Refine event ideation and motivate users to engage with events in a given meta of your game that distributes rewards but also maintains engagement and drives monetization.

A/B Testing: Modify config files to implement A/B tests that compare different game settings. For example, one player group might receive more in-game currency as a daily reward, while another group receives less. Then compare retention and spending between the two groups to determine which configuration is more effective.

Event Configuration: Special in-game events can be activated or modified via these configuration changes. This can include setting the start and end times of events, the type of rewards offered, and any special rules or mechanics for the event.