GameAnalytics Integration for Mobile Games: Tracking and Analytics

Players progress through levels, but you don't know where they drop off? Built-in metrics from App Store and Google Play don't show in-game behavior. We specialize in GameAnalytics integration — a platform designed for mobile games — so you can see every progression funnel, every currency spend, and every ad session. Our team has over 7 years of experience and has completed 150+ GameAnalytics integrations for mobile games. Get a consultation — discuss the details of integration for your project.

Why GameAnalytics Beats Universal Systems

GameAnalytics is built for games from the ground up. Progression, resource, and design events are its native data model. No need to design a schema from scratch. Setup time is reduced by 2 days on average. License cost under high load is 2–3 times lower than Amplitude. At 10 million events per month, license savings reach 80%. Compared to custom analytics, GameAnalytics integration is 3x faster and 5x more cost-effective. GameAnalytics documentation

How GameAnalytics Improves Retention

Automatic Day 1, 7, and 30 reports show player retention dynamics. Level progression funnels pinpoint the exact churn point. For example, after optimizing level 5 for one of our clients, Day 14 retention increased by 20%. Clients typically see up to 30% improvement in retention within the first month after integration.

How to Monitor Monetization

Resource events track all currency sources and sinks, giving full monetization tracking. GameAnalytics automatically builds an economy balance: if sinks significantly exceed sources, players quickly become poor and leave. We configure these events for you and provide recommendations for balancing.

SDK Integration

SDKs are available for Unity (GameAnalytics SDK Unity v6.2.0), iOS (GameAnalytics iOS), Android (GameAnalytics Android), and React Native. Follow these steps to integrate:

1. Install the SDK via Package Manager or download .unitypackage.
2. Add the GameAnalytics component to a GameObject in your first scene.
3. Enter your Game Key and Secret Key from the dashboard into the component.
4. Call GameAnalytics.Initialize() in the Awake method of your GameManager.

For Unity — via Package Manager or .unitypackage:

using GameAnalyticsSDK;

public class GameManager : MonoBehaviour
{
    void Awake()
    {
        GameAnalytics.Initialize();
    }
}

Before calling Initialize(), the GameAnalytics component must be in the scene with Game Key and Secret Key from the dashboard filled in.

On iOS natively:

import GameAnalytics

GameAnalytics.configureBuild("1.0.0")
GameAnalytics.initialize(withGameKey: "GAME_KEY", gameSecret: "SECRET_KEY")

Event Types (table)

Progression and Resource can be combined in one code block:

// Level start
GameAnalytics.NewProgressionEvent(GAProgressionStatus.Start, "world_1", "level_05");
GameAnalytics.NewResourceEvent(GAResourceFlowType.Source, "gold", 500, "reward", "daily_bonus");

Design covers everything else:

GameAnalytics.NewDesignEvent("Boss:Defeated:DragonKing", 1);
GameAnalytics.NewDesignEvent("Settings:SoundToggle", 0); // 0 = disabled

How to Add a Design Event for a Custom Mechanic (Step by Step)

1. Define the hierarchy using colons (max 5 levels).
2. Call GameAnalytics.NewDesignEvent("your:event:path", value).
3. Verify the event appears in the GameAnalytics Dashboard.

Avoiding Event Naming Mistakes

The event string is separated by colons — these are hierarchy levels in the dashboard. Boss:Defeated:DragonKing creates a branch Boss → Defeated → DragonKing. Max 5 levels. If you don't maintain structure from the start, the dashboard becomes a flat list of hundreds of lines.

Automatic Metrics

GameAnalytics collects DAU/MAU, retention (Day 1, 7, 30), session length, and crash reports (via native crash handler integration) without extra code. For iOS 14+ SKAdNetwork support is enabled automatically. These automatic game metrics are critical for product evaluation.

Common integration mistakes:

• Naming Design events without hierarchy — dashboard becomes flat.
• Missing explicit session end on iOS for background tasks.
• Incorrect Game Key and Secret Key mapping for different builds.

Integration Stages

Session End Validation

GameAnalytics automatically closes a session when the app goes to background via OnApplicationPause. On Android this works reliably. On iOS, under certain scenarios (VoIP, Background Fetch), the session may not close. Add an explicit call:

void OnApplicationPause(bool paused)
{
    if (paused) GameAnalytics.StopSession();
    else GameAnalytics.StartSession();
}

The free GameAnalytics plan suits most indie games — event limits are high enough (500 million events per month). This makes it attractive for projects without a budget for Amplitude or Mixpanel.

What's Included

• SDK integration (Unity / iOS / Android)
• Configuration of progression events for each game world and level
• Configuration of resource events for all currency sources and sinks
• Design events for key mechanics (bosses, items, settings)
• Data verification in GameAnalytics Dashboard

Timelines

Basic setup with core event types: 0.5–1 day. Cost is calculated individually. We guarantee transparent analytics with no hidden costs. Contact us to discuss your project.

Mobile App Analytics: Firebase, Amplitude, AppsFlyer and Attribution

Our team regularly encounters projects where analytics is already "set up" but yields no real insights. A typical example is a startup with 50k DAU: tracking dozens of events without a single answer to the question "why don't users reach payment?". In two weeks we built a basic funnel and found that 70% of users drop off at the phone number verification screen. After fixing the bug, retention increased by 12%. The takeaway: analytics should start with specific questions, not tracking everything indiscriminately.

Why Event Taxonomy is the Foundation of Mobile App Analytics?

Firebase Analytics, Amplitude, Mixpanel — technically similar. The difference lies in what you put into them. A common mistake: events like screen_view, button_tap_1, button_tap_2 without context. A month later, no one remembers what button_tap_2 means.

Proper taxonomy: object + action + context. product_viewed, checkout_started, payment_completed with parameters product_id, category, price, source. This allows building funnels, cohort analysis, and retention without additional tracking.

We document the naming convention in a tracking plan — a document (Google Sheet or Amplitude Data Catalog) describing every event, its parameters, and triggering conditions. The tracking plan is synced with the analytics team before development begins, not after. This approach ensures that data remains interpretable months later and doesn't become a dump. Experience from 50+ projects confirms: without a tracking plan, analytics maintenance costs increase 2-3 times due to rework.

What Should You Choose for Mobile App Analytics: Firebase, Amplitude, or Mixpanel?

The table below highlights key differences between the three popular platforms. Choice depends on budget, traffic, and tasks.

Firebase Analytics — free, deep integration with Google Ads, BigQuery export for raw data. Limitations: data latency up to 24 hours, limited funnels. For startups with Google Ads traffic, it's the first choice.

Amplitude — product analytics focused on cohorts and user journeys. Journeys (formerly Pathfinder) shows actual paths between events — not assumed funnels but real routes. Session Replay records sessions for UX analysis. The free tier up to 10M events/month is enough for most products at launch.

Mixpanel — close to Amplitude, stronger in real-time segmentation. Insights, Funnels, Retention cover 90% of product analysts' tasks.

How to Solve Multi-Channel Attribution with AppsFlyer?

Knowing where a user came from is a separate task. Firebase Attribution works only within the Google ecosystem. For multi-channel attribution (Facebook Ads, TikTok, Apple Search Ads, programmatic), an MMP (Mobile Measurement Partner) is needed.

AppsFlyer is the market leader. OneLink — universal deep link working on iOS and Android, correctly attributing installs from any channel. Protect360 — built-in fraud protection (fake installs, click injection on Android). Adjust and Branch are competitors with similar features. Branch excels in deep linking; Adjust is popular in gaming.

According to Apple, with iOS 14.5, apps must obtain user permission via ATT before collecting IDFA for tracking. AppsFlyer uses probabilistic matching (IP + user agent + timing) for these users — accuracy is lower but better than nothing. SKAdNetwork and Privacy Preserving Attribution provide aggregated data from Apple with a 24-72 hour delay.

How to Set Up Crash Analytics to Not Miss Bugs?

Firebase Crashlytics is the standard for crash reporting. It automatically groups crashes by stack trace, shows affected users %, and sends velocity alerts when crash rate increases by more than 10% per hour.

Important: symbolication. On iOS, .dSYM files must be automatically uploaded with each build — via Fastlane upload_symbols_to_crashlytics or Xcode Cloud built-in. Without symbols, crashes in Crashlytics appear as memory addresses. This happens more often than expected when switching to a new CI — in one project with 500k users, we found that 40% of crashes remained unsymbolicated due to a missing CI/CD step. After automation, bug response time dropped from 3 hours to 15 minutes.

For React Native and Flutter, @sentry/react-native and sentry_flutter provide additional context: breadcrumbs, network requests before the crash, Redux/Provider state.

Below is a comparison of popular crash analytics tools to choose according to your needs.

Environment Setup

Three environments with separate Firebase projects: dev, staging, production. Mixing analytics from test sessions and production is a common mistake that skews all metrics. On iOS via GoogleService-Info.plist per scheme, on Android via google-services.json in each flavor folder.

Timelines: basic analytics with Firebase + Crashlytics — 3-5 days. Full tracking plan + Amplitude/Mixpanel with funnels and cohorts — 2-3 weeks. Attribution via AppsFlyer with deep linking and fraud protection — 1-2 weeks. Cost is calculated individually based on integration complexity.

What Is Included in Our Work

As part of analytics implementation, we provide:

• Development and approval of a tracking plan with product and marketing teams.
• SDK integration (Firebase, Amplitude, Mixpanel, AppsFlyer) considering your stack (Swift/Kotlin/Flutter/React Native).
• Setup of funnels, cohorts, dashboards, and alerts.
• Automation of symbolication and .dSYM upload via Fastlane.
• Documentation of events and parameters.
• Team training on the analytics platform.
• Two weeks of post-release support and tracking adjustments.

Our experience: 7 years of analytics implementation and over 80 successful projects in mobile development. We guarantee data correctness and transparency at every stage.

Contact us for a consultation on setting up analytics for your app. Request an audit of your current analytics — and we will show you which metrics you are losing.