Every live-service game runs on a stream of data most players never think about: which level they quit on, how long they hesitate before a purchase prompt, whether Day 7 retention is climbing or sliding. Three platforms dominate how studios capture that data in 2026, and they’ve priced themselves in ways that punish the wrong choice. Unity Gaming Services Analytics charges nothing until you cross 50,000 monthly active users, then bills as low as $0.00225 per MAU at scale. GameAnalytics stays free indefinitely on its Core tier but gates advanced tooling behind add-ons running up to $499 a month. And Microsoft is quietly retiring a chunk of Azure PlayFab’s analytics stack — PlayFab Insights Management shuts down on March 31, 2026, forcing any studio still leaning on it to plan a migration now, not later.
This comparison walks through what each platform actually costs at different player-count tiers, how their data retention and SDK support differ, and what the PlayFab Insights Management retirement means if your studio is one of the teams still using it.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
Why Game Analytics Platforms Matter More Than Ever in 2026
Live-ops decisions — when to run an event, which players are about to churn, whether a new onboarding flow actually improved Day 1 retention — all depend on telemetry pipelines that most studios don’t want to build from scratch. That’s the market Unity Gaming Services Analytics, GameAnalytics, and Azure PlayFab Insights compete in, alongside general-purpose product analytics tools like Amplitude that some studios adopt instead of a games-specific platform.
Choosing wrong isn’t just a billing headache. A studio that builds its live-ops dashboards, retention alerts, and monetization funnels around one vendor’s event schema faces real engineering cost if it later needs to switch, since custom event names, session definitions, and cohort logic rarely map cleanly from one platform to another. That’s part of why the PlayFab Insights Management retirement matters beyond the studios directly affected: it’s a concrete reminder that even a Microsoft-backed platform can sunset a specific analytics layer with a hard date, and any team picking a vendor today should weigh that platform risk alongside price.
All three game-specific platforms remain active in 2026, but they’re not standing still. Unity’s Analytics pricing documentation, updated January 26, 2026, confirms a shift to a pure pay-as-you-go, MAU-metered model with no flat monthly plan. GameAnalytics expanded its paid tier lineup with a suite of “IQ” products — AnalyticsIQ, MarketIQ, PipelineIQ, and SegmentIQ — that sit on top of its free core analytics. And Microsoft’s own documentation states plainly that “PlayFab Insights Management will be retired 3/31/2026,” a deprecation notice studios need to account for regardless of which platform they ultimately choose.
Unity Gaming Services Analytics: MAU-Metered Pricing
Unity Gaming Services Analytics runs on a strict pay-as-you-go model tied to monthly active users, with no fixed monthly plan price. Unity’s own pricing page includes 50,000 active users per month, 500 custom events per MAU, and 0.05 query seconds per MAU in its free tier. Cross that MAU threshold and the per-user rate steps down as you scale, according to Unity’s MAU-based pricing documentation (updated January 26, 2026):
- 0 – 50,000 MAU: free
- 50,001 – 150,000 MAU: $0.00360 per MAU
- 150,001 – 500,000 MAU: $0.00315 per MAU
- 500,001 – 1,000,000 MAU: $0.00293 per MAU
- 1,000,001 – 5,000,000 MAU: $0.00225 per MAU
- 5,000,001+ MAU: contact Unity Support
Because Unity Analytics is billed purely on active users rather than a subscription tier, a title with 200,000 MAU pays roughly $472.50 a month for analytics alone (the 150,000 users past the free tier’s 50,000 threshold, times the applicable per-MAU rate across those bands) — a bill that scales linearly with your player base rather than jumping between plan tiers. Unity’s data FAQ documentation also draws a distinction in how long data sticks around: raw event data is retained for 13 months and then automatically deleted, while aggregated metric data (DAU, MAU, session length, and dashboard/user-profile data) persists until a player or developer explicitly requests its removal. Unity’s privacy overview confirms the same 13-month default for personal data, with shorter retention available by contacting support, and a dedicated deletion event that removes all of a specific player’s data within 30 days upon request.
Because Analytics ships as part of the broader Unity Gaming Services suite, integration is tightest for studios already building in the Unity engine — Unity’s own documentation frames Analytics as a native dashboard and SDK layer rather than a bolt-on third-party service, which matters if your team is choosing an analytics vendor at the same time it’s choosing a game engine.
GameAnalytics: Free Core, Paid IQ Add-Ons
GameAnalytics takes the opposite pricing philosophy: a forever-free Core tier with no stated MAU cap in its marketing copy, then a set of named paid products layered on top for studios that need more than baseline event tracking. According to G2’s pricing page (updated August 29, 2026), the current lineup runs:
- Core: $0 per month
- AnalyticsIQ Pro: $29 per month (G2) — a separate CostBench analysis lists this add-on at $49/month, a discrepancy likely tied to billing term or a pricing update between snapshots
- MarketIQ Pro: $299 per month (G2), with CostBench citing $499/month for the same product
- PipelineIQ Pro: $499 per month
- SegmentIQ Pro: custom “Contact Us” pricing
GameAnalytics’ SDK coverage is broader than either competitor for engines beyond Unity. Its SDKs Overview documentation (updated August 23, 2026) lists native integrations for Unity (Android, iOS, HTML5, Linux, tvOS, UWP, Windows), Cocos2D, GameMaker, Cordova, and Flutter, plus standalone platform SDKs for Android, iOS, Meta Quest 2, and tvOS, and language-level SDKs in JavaScript, C++, and C#. Its Godot SDK separately supports iOS, Android, Web, Windows, Mac, and Linux — engine breadth that neither Unity Analytics (Unity-only) nor PlayFab’s documentation set explicitly matches in the sources available.
Data retention on GameAnalytics degrades in stages rather than disappearing on a single cutoff date. Its retention policy (dated March 18, 2026, updated June 23, 2026) specifies that full metrics and filters remain available for data up to one month old; between one and three months, some granular data such as error stack traces becomes unavailable; between three and twelve months, certain event types and filtering dimensions are further restricted; and beyond twelve months, only aggregate counts survive for a limited set of event types like revenue and ad impressions. For studios using the PipelineIQ data warehouse add-on, checkpoint datasets hold up to a year of data while event tables cap out at 30 days.
Azure PlayFab Insights: The March 2026 Retirement
PlayFab’s analytics stack is billed differently from both competitors — through a credit system rather than a flat MAU or subscription rate. Every title starts on Performance Level 1, a free tier included with all PlayFab plans, according to Microsoft’s Insights overview documentation. Beyond that, Microsoft’s PlayFab pricing page (dated February 27, 2026) lists Insights Credits at $0.72 per credit on pay-as-you-go, with the Standard plan including 25 free credits before $0.65 per additional credit, and the Premium plan including 750 free credits before $0.62 per additional credit.
Event ingestion overages are billed at one credit per 2.7 million events or rows written beyond your plan’s included allotment, and long-term storage retention runs 50 credits per terabyte-month, charged only for data actually retained. The default retention window is 30 days, which Microsoft’s documentation notes “fulfills most GDPR compliance regulations,” though studios can extend or shorten that window globally or per data table.
The critical fact for any studio currently on PlayFab: Microsoft’s own Insights documentation states directly that “PlayFab Insights Management will be retired 3/31/2026.” That’s specifically the Insights Management layer — the management and configuration tooling around Insights — not the entire PlayFab platform or its core analytics and telemetry ingestion, which continues to be documented with active performance-level and retention settings through mid-2026. But for any team that built dashboards, automation, or reporting workflows against Insights Management specifically, this is a hard deadline, not a distant possibility.
Side-by-Side Specs Comparison
| Attribute | Unity Gaming Services Analytics | GameAnalytics | Azure PlayFab Insights | Amplitude (generic alternative) |
|---|---|---|---|---|
| Pricing model | Pure MAU pay-as-you-go | Free core + named paid add-ons | Credit-based (Insights Credits) | MTU + event-metered SaaS tiers |
| Free tier | 50,000 MAU/month | Unlimited on Core plan (no stated MAU cap) | Performance Level 1 (free, included in all plans) | 10,000 MTU + 2M events/month |
| Entry paid rate | $0.00360/MAU (50,001–150,000 band) | AnalyticsIQ Pro: $29–$49/month | $0.72/credit pay-as-you-go | $49/month (Plus), $0.049/MTU up to 300K MTU |
| Top-tier named add-on | N/A (scales continuously) | PipelineIQ Pro: $499/month | Premium: 750 free credits, $0.62/additional credit | Growth/Enterprise: custom pricing |
| Data retention (raw events) | 13 months, then auto-deleted | Full detail to 1 month; degrades in stages to 12+ months | 30 days default, configurable per table | Not specified in dated sources |
| 2025–2026 major change | MAU-based pricing model formalized (Jan 2026 docs) | Added AnalyticsIQ/MarketIQ/PipelineIQ/SegmentIQ suite | Insights Management retiring March 31, 2026 | Pricing docs updated March 24, 2026 |
| Engine/SDK breadth | Unity-native (part of Unity Gaming Services) | Unity, Cocos2D, GameMaker, Cordova, Flutter, Godot, native mobile | Client/server SDKs across major engines (not itemized in dated docs) | Client SDKs + server APIs (not games-specific) |
| Event limit (free tier) | 500 custom events per MAU | Not explicitly capped in marketing copy | Included ingestion volume varies by performance level | 2,000,000 events/month (Free plan) |
| Query performance (free tier) | 0.05 query seconds per MAU | Not specified in dated sources | Billed per credit for query/processing usage | Not games-specific; standard dashboard queries |
| Storage retention cost | Included in MAU rate up to 13 months | Included; degrades by data type over time | 50 credits per terabyte-month beyond default window | Not specified in dated sources |
| Best fit | Unity-first studios wanting native integration | Multi-engine studios wanting a free baseline plus optional paid depth | Studios already on PlayFab’s broader multiplayer/backend stack | Studios wanting general product analytics beyond games |
The pricing-model mismatch here matters more than any single number. Unity’s continuous per-MAU rate means costs rise smoothly and predictably with player count. GameAnalytics’ named-tier model means you pay a flat fee once you need a specific capability, regardless of exact user count. PlayFab’s credit system ties cost to actual event volume and storage, which can reward lean event schemas but punish verbose logging. None of these map cleanly onto each other, so the “cheapest” platform depends entirely on your title’s MAU curve and how many custom events you fire per session.
Pricing at Scale: What a Growing Title Actually Pays
| Player scale | Unity Gaming Services Analytics (est.) | GameAnalytics (est.) | Azure PlayFab Insights (est.) |
|---|---|---|---|
| Indie / pre-launch (10,000 MAU) | $0 (within free tier) | $0 (Core plan) | $0 (Performance Level 1) |
| Small live title (75,000 MAU) | ~$90/month (25,000 MAU past free tier × $0.00360) | $0–$29–$49/month if AnalyticsIQ Pro is needed | Depends on event volume; likely within Standard’s 25 free credits |
| Mid-size hit (300,000 MAU) | ~$787.50/month (blended across 50K–150K and 150K–300K bands) | $29–$499/month depending on IQ add-ons needed | Scales with event ingestion; overage at 1 credit/2.7M events |
| Large title (1,000,000 MAU) | ~$2,721/month (blended across all bands to the 1M mark) | Up to $499/month + custom SegmentIQ pricing if needed | Premium plan: 750 free credits, then $0.62/credit |
| Breakout hit (5,000,000+ MAU) | Contact Unity Support for custom pricing | Custom “Contact Us” pricing (SegmentIQ) | Scales via credit consumption; storage at 50 credits/TB-month |
These are directional estimates built from each vendor’s published rate cards, not quotes from a sales call, since actual bills depend heavily on custom event volume, query frequency, and how much historical data you choose to retain. The Unity figures are the most mechanically predictable of the three because the pricing model has no hidden variables beyond raw MAU count; GameAnalytics and PlayFab both depend more on usage patterns that vary title to title.
Data Retention Compared: How Long Your Player Data Actually Lives
Retention policy is easy to overlook during vendor selection and expensive to discover too late, especially for studios subject to GDPR, COPPA, or platform-specific data handling rules. The three platforms handle this in meaningfully different ways.
Unity’s approach splits data into two buckets with different lifespans: raw event data expires automatically after 13 months, while aggregated dashboard metrics and user profiles persist indefinitely until someone explicitly requests deletion. That’s a reasonable default for year-over-year retention analysis, but it means raw event-level debugging of a problem older than 13 months simply isn’t possible — you’re left with whatever aggregates survived.
GameAnalytics takes a graduated-decay approach instead of a hard cutoff: full granularity for a month, partial granularity (missing stack traces and some filters) from one to three months, further restriction from three to twelve months, and aggregate-only survival past a year for a narrow set of event types. This design means recent-data debugging is excellent, but historical trend analysis beyond a year is limited to whatever aggregate categories GameAnalytics chose to preserve long-term.
PlayFab’s default is the shortest of the three at 30 days, explicitly framed by Microsoft as sufficient for “most GDPR compliance regulations” rather than as a technical limitation — studios that want longer retention configure it explicitly and pay the 50-credits-per-terabyte-month storage rate for the extension. That makes PlayFab’s retention model the most deliberately cost-gated of the three: you decide how much history is worth paying to keep, rather than inheriting a fixed default window.
Real-World Use Cases and Studio Scenarios
Five patterns show up repeatedly in how studios actually pick between these platforms, based on the pricing and architecture differences above:
- Unity-first indie studios typically default to Unity Gaming Services Analytics simply because it’s already available inside the engine they’re using, and the 50,000 MAU free tier covers most pre-launch and early-access titles without any billing setup at all.
- Cross-engine studios shipping to Unity, Godot, and native mobile simultaneously lean toward GameAnalytics specifically because its SDK coverage spans engines that Unity Analytics simply doesn’t reach, letting one analytics vendor serve a portfolio of titles built on different engines.
- Studios already running multiplayer backend, matchmaking, or player-data services on Azure PlayFab often keep Insights for analytics purely for billing and infrastructure consolidation, even though the March 2026 Insights Management retirement means they need to plan around that specific component’s shutdown.
- Studios that outgrew a free tier and need deeper segmentation or cohort analysis without paying GameAnalytics’ higher IQ-tier prices sometimes migrate to Amplitude instead, accepting a non-games-specific tool in exchange for its Free plan’s 10,000 MTU and 2 million events per month, or its Plus plan’s per-MTU metered pricing.
- Studios anywhere near the PlayFab Insights Management deprecation should treat March 31, 2026 as a hard planning deadline: export any dashboards, automations, or reports built against Insights Management and rebuild them against whichever platform — PlayFab’s core Insights, or a full switch to Unity Analytics or GameAnalytics — will carry that workload going forward.
AI Features and Data Infrastructure in 2026
All three vendors are pushing AI-assisted features into their 2026 roadmaps, though the depth of what’s actually shipped varies. GameAnalytics’ integrations page, updated August 26, 2026, specifically calls out “early access to AI features” alongside its expanded SDK and integration catalog, positioning AI-assisted analysis as a near-term addition to its core dashboards rather than a shipped, generally available capability. Amplitude has moved further here: its 2026 pricing and feature documentation lists AI Feedback and predictive audiences as included capabilities across multiple plan tiers, reflecting Amplitude’s broader position as a general product-analytics platform investing more heavily in AI-driven insight generation than the games-specific competitors in this comparison.
Underlying data infrastructure is also worth knowing before you commit, particularly for studios with data-residency requirements. Unity’s own support documentation confirms that Analytics data is stored at rest in Google Cloud Platform’s europe-west4 region, with replication to GCP’s us-central1 region when Analytics Data Access is enabled — a detail that matters for European studios or publishers with contractual data-location requirements. GameAnalytics and PlayFab’s dated documentation sets available for this comparison don’t specify equivalent data-residency details as explicitly, so studios with strict compliance needs should confirm current hosting regions directly with each vendor before finalizing a migration.
Event Tracking, Custom Properties, and Query Limits
The free-tier fine print differs enough between these platforms that it’s worth reading before you architect an event schema around any one of them. Unity’s free tier documentation is the most specific of the three: 500 custom events per MAU and 0.05 query seconds per MAU, both included in the 50,000 MAU free allotment. That’s a hard technical ceiling — a highly chatty event schema that fires closer to 1,000 events per active user will burn through that allotment faster than a leaner schema, independent of your actual MAU count.
GameAnalytics doesn’t publish an explicit numeric cap on events per user in its dated marketing and documentation, framing its Core tier instead around unrestricted event tracking with retention-based limits on how long that data stays queryable at full granularity. PlayFab ties its limits to ingestion volume rather than per-user event counts, billing overages at one credit for every 2.7 million events or rows written past your plan’s included allowance — a model that rewards studios with smaller, well-structured event payloads and penalizes verbose logging patterns like firing a separate event for every frame of a physics interaction.
Amplitude’s free tier caps out at 2 million events per month across up to 10,000 monthly tracked users, which works out to roughly 200 events per tracked user if you’re running near the ceiling on both dimensions simultaneously — a tighter effective allowance than Unity’s per-MAU figure once you actually do the math, though Amplitude’s paid tiers scale that allowance up considerably as MTU count grows.
Migration Guide: Moving Off PlayFab Insights Management Before March 2026
If your studio depends on PlayFab Insights Management for dashboards, scheduled reports, or data exploration tooling, here’s the practical path to move before the March 31, 2026 retirement date.
- Inventory everything built on Insights Management specifically. Distinguish between the Insights Management layer (being retired) and core PlayFab event ingestion and Insights Credits billing (which continues), since only the management/configuration tooling is affected.
- Export existing dashboard and report configurations. Document the exact queries, visualizations, and scheduled exports currently running so they can be rebuilt rather than reverse-engineered after the fact.
- Decide whether to stay on PlayFab’s core Insights or migrate analytics entirely. If your team wants to keep using PlayFab’s underlying event data and credit-based billing, you’ll rebuild management workflows using PlayFab’s remaining tooling. If you want to leave PlayFab analytics altogether, this is the natural point to evaluate Unity Analytics or GameAnalytics instead.
- If staying on PlayFab, review your current Performance Level and Insights Credits usage. Confirm whether your Standard or Premium plan’s free credit allotment (25 or 750 credits respectively) still covers your ingestion volume before rebuilding dashboards on the surviving tooling.
- If migrating to Unity Analytics, plan for the MAU-based billing model. Map your current player count against Unity’s per-MAU pricing bands ($0.00360 down to $0.00225 per MAU) to estimate the new monthly cost before committing engineering time to the SDK integration.
- If migrating to GameAnalytics, start on the free Core tier. Validate that Core’s baseline event tracking covers your minimum viable analytics needs before evaluating whether AnalyticsIQ Pro, MarketIQ Pro, or PipelineIQ Pro are worth their respective $29–$499/month price points.
- Re-implement your event schema in the new platform’s SDK. Custom event names, properties, and funnels rarely map one-to-one between PlayFab, Unity Analytics, and GameAnalytics, so budget real engineering time for this step rather than treating it as a drop-in SDK swap.
- Run both systems in parallel for at least one full reporting cycle. Compare Day 1, Day 7, and Day 30 retention numbers between the old and new pipeline before fully cutting over, since subtle differences in session definitions can shift your headline retention metrics.
- Rebuild any automated alerts or live-ops triggers. If Insights Management fed automated decisions (churn-risk alerts, live-ops event triggers), these need explicit rebuilding in the new platform rather than assuming equivalent tooling exists out of the box.
- Confirm data retention settings match your compliance requirements. Whichever platform you land on, explicitly configure retention windows (13 months on Unity, graduated decay on GameAnalytics, or a configured window on PlayFab) rather than assuming the default matches what your previous setup provided.
Pros and Cons: Unity Gaming Services Analytics
Pros: Native integration for Unity-based titles, a generous 50,000 MAU free tier, continuous and predictable per-MAU pricing with no plan-tier cliffs, and clear documentation on both event limits (500 custom events per MAU) and query performance (0.05 query seconds per MAU) in the free tier.
Cons: Tightly coupled to the Unity engine with no clear path for multi-engine studios, costs rise indefinitely with MAU growth rather than flattening at a fixed enterprise rate until you separately contact Unity Support, and the 13-month raw-event retention window is fixed rather than configurable without contacting support.
Pros and Cons: GameAnalytics
Pros: A genuinely free Core tier with no stated MAU ceiling in current marketing copy, the broadest engine and SDK coverage of the three platforms (Unity, Cocos2D, GameMaker, Cordova, Flutter, Godot, and native mobile), and granular, well-documented data retention behavior by data type and age.
Cons: Advanced capabilities are locked behind named paid tiers that can reach $499/month for PipelineIQ Pro, pricing figures vary between sources (G2 and CostBench cite different rates for the same AnalyticsIQ and MarketIQ products), and studios needing enterprise-scale segmentation must contact sales for SegmentIQ rather than seeing transparent published pricing.
Pros and Cons: Azure PlayFab Insights
Pros: Tight integration for studios already using PlayFab’s broader multiplayer and backend services, a free Performance Level 1 tier included with every PlayFab title, and a storage-retention model that lets studios pay only for the historical depth they actually want.
Cons: Insights Management retires March 31, 2026, forcing a hard migration deadline on any team using that specific tooling, the default 30-day retention window is the shortest of the three platforms, and credit-based billing is harder to forecast than a straightforward MAU or flat-tier model since it depends on granular event and row-write volume.
How These Platforms Compare to General-Purpose Analytics Tools
Some studios skip games-specific analytics entirely and adopt a general product-analytics platform like Amplitude, which offers a Free (Starter) plan covering 10,000 monthly tracked users and up to 2 million events per month, according to Amplitude’s own pricing page (updated September 5, 2026). Its Plus plan starts at $49/month billed annually, with a metered rate of $0.049 per MTU up to 300,000 MTUs or 25 million events, while Growth and Enterprise tiers are custom-priced.
The tradeoff is real: Amplitude wasn’t built for games specifically, so it lacks the pre-built retention curves, funnel templates, and event taxonomies that GameAnalytics and Unity Analytics ship with out of the box. But for studios that already use Amplitude for a companion mobile app, website, or other non-game product, consolidating analytics vendors can outweigh the loss of games-specific tooling — particularly for hybrid-casual studios where the line between “game” and “app” is blurry anyway.
Cost Optimization Strategies for Each Platform
Regardless of which platform a studio picks, the same broad principle applies: analytics costs track event volume and player count, so the biggest lever is almost always trimming what you track, not negotiating a better rate.
On Unity Gaming Services Analytics, the most direct lever is staying disciplined about MAU definitions — since Unity counts any unique user ID that logs at least one session in a month, studios running frequent beta or test builds under separate project IDs can inadvertently inflate their billed MAU count. Consolidating test and QA traffic under a separate, non-production Unity project keeps that noise out of the billed player count entirely. The second lever is event discipline: since the free tier caps out at 500 custom events per MAU, trimming redundant or duplicate events (firing both a “level_start” and a near-identical “level_begin” event, for instance) directly extends how far the free tier stretches before per-MAU billing kicks in.
On GameAnalytics, the clearest optimization is starting on Core and only adding a specific IQ product once you’ve identified the exact capability gap it fills — PipelineIQ Pro’s $499/month data warehouse access, for example, is a meaningful expense that only pays for itself if your team actually needs raw data export into an external warehouse for custom analysis Core’s dashboards can’t provide. The second lever is understanding the platform’s own data-decay schedule: since granular data (like error stack traces) becomes unavailable after just one to three months regardless of plan, there’s no cost benefit to over-provisioning storage for data GameAnalytics itself will restrict access to on a fixed schedule.
On PlayFab, the credit-based model rewards lean event schemas directly: since overages bill at one credit per 2.7 million events, consolidating multiple small events into fewer, richer events (attaching several properties to one event rather than firing three separate single-property events) can meaningfully reduce total event count without losing any actual data fidelity. The second lever is retention tuning — since storage costs 50 credits per terabyte-month beyond the included allowance, deliberately shortening retention on high-volume, low-value event types (verbose debug logging, for instance) while keeping longer retention on business-critical events (purchases, session starts) can cut storage costs without sacrificing the data that actually drives live-ops decisions.
Which Platform Should You Choose? Use-Case Recommendations
- Choose Unity Gaming Services Analytics if: your title is built in Unity, you want native SDK integration without a third-party dependency, and you’re comfortable with continuous MAU-based billing rather than fixed plan tiers.
- Choose GameAnalytics if: you’re shipping across multiple engines (Unity, Godot, Cocos2D, GameMaker), want to start completely free with no MAU ceiling, and can accept paying for specific advanced capabilities (segmentation, data warehousing, market benchmarking) only as your studio actually needs them.
- Choose Azure PlayFab Insights if: your backend, matchmaking, and player-data services already run on PlayFab and you want analytics under the same billing relationship, but budget migration time now for the March 31, 2026 Insights Management retirement.
- Choose Amplitude if: your studio already uses it for a non-game product and wants a single analytics vendor across your portfolio, or you specifically need advanced product-analytics features like session replay and web experimentation that games-specific platforms don’t offer.
- Avoid building new dashboards or automation on PlayFab Insights Management starting now: with a confirmed March 2026 retirement date, any new investment in that specific tooling has a built-in expiration.
The Verdict: What the Data Actually Shows
There’s no single winner here because the three platforms optimize for different studio profiles. Unity Gaming Services Analytics is the simplest choice for Unity-only studios that want predictable, continuously scaling costs and are willing to accept engine lock-in. GameAnalytics offers the best free tier and the widest engine support of the three, but its paid tier pricing is the least consistent across sources, with the same products quoted at different rates by G2 and CostBench within the same month. Azure PlayFab Insights makes the most sense for studios already committed to PlayFab’s broader backend stack, but the March 31, 2026 retirement of Insights Management is a real, dated deadline that should factor into any decision to expand PlayFab analytics usage today.
The practical takeaway: model your actual MAU curve and event volume against each platform’s specific pricing mechanics rather than comparing headline free-tier numbers, since Unity’s continuous per-MAU rate, GameAnalytics’ named-tier add-ons, and PlayFab’s credit system all reward different usage patterns. And if PlayFab Insights Management is part of your current stack, the migration conversation needs to start well before March 2026, not after.
Frequently Asked Questions
Is PlayFab Insights being shut down?
Not entirely. Microsoft’s documentation states that “PlayFab Insights Management will be retired 3/31/2026.” That refers specifically to the Insights Management layer — the configuration and management tooling around Insights — not PlayFab’s core analytics, event ingestion, or Insights Credits billing, which continue to be documented as active through mid-2026.
How much does Unity Gaming Services Analytics cost?
It’s free for up to 50,000 monthly active users. Beyond that, pricing scales per MAU: $0.00360 for the 50,001–150,000 band, $0.00315 for 150,001–500,000, $0.00293 for 500,001–1,000,000, and $0.00225 for 1,000,001–5,000,000 MAU. Above 5 million MAU, Unity directs studios to contact its support team for custom pricing.
Is GameAnalytics really free?
The Core plan is free with no MAU limit stated in current marketing materials, according to GameAnalytics’ own pricing page and G2’s pricing breakdown (updated August 29, 2026). Advanced capabilities require paid add-ons: AnalyticsIQ Pro ($29–$49/month depending on the source), MarketIQ Pro ($299–$499/month), PipelineIQ Pro ($499/month), and SegmentIQ Pro (custom “Contact Us” pricing).
How long does each platform retain player data?
Unity Analytics retains raw event data for 13 months before automatic deletion, while aggregated metrics persist until deletion is requested. GameAnalytics uses a graduated decay: full detail for one month, partial detail through three months, further restriction through twelve months, and aggregate-only data beyond a year for a limited set of event types. PlayFab Insights defaults to 30 days, extendable at a cost of 50 credits per terabyte-month for additional storage.
Which game analytics platform supports the most game engines?
GameAnalytics has the broadest documented engine support among the three, with native SDKs for Unity, Cocos2D, GameMaker, Cordova, Flutter, and Godot, plus standalone platform SDKs for Android, iOS, Meta Quest 2, and tvOS. Unity Gaming Services Analytics is tied specifically to the Unity engine.
Should I switch from PlayFab Insights to Unity Analytics or GameAnalytics?
Only if you’re leaving PlayFab’s broader ecosystem entirely, or if the specific Insights Management features you rely on aren’t rebuildable on PlayFab’s surviving Insights tooling. If your studio’s backend, matchmaking, and player data already run on PlayFab, it’s often simpler to rebuild your dashboards and automation using PlayFab’s remaining analytics tooling rather than migrating the entire pipeline to a different vendor.
What is Amplitude’s free tier, and is it good enough for a game studio?
Amplitude’s Free (Starter) plan covers 10,000 monthly tracked users and up to 2 million events per month, plus features like Session Replay (1,000 sessions/month), unlimited feature flags, and web experimentation. It can work for smaller titles or hybrid-casual studios, but it lacks the games-specific retention curves and funnel templates that GameAnalytics and Unity Analytics provide out of the box.
What happens to my historical PlayFab Insights data after March 2026?
Microsoft’s documentation specifies the retirement applies to Insights Management, not the underlying event data or Insights Credits billing system. Studios should still export any dashboard configurations, saved queries, and reports built specifically within Insights Management before the March 31, 2026 date, since that management layer itself is what’s being discontinued.
Related Coverage
- Codespaces vs Gitpod vs Cloud Workstations: $199 Gap [2026]
- SNS vs SQS vs EventBridge: 4x Message Size Gap [2026]
- Confluent vs MSK vs Redpanda: 46x Kafka Price Gap [2026]
- LaunchDarkly vs Unleash vs GrowthBook: $2,800 Gap [2026]
- DigitalOcean vs Vultr vs Lightsail: 2.2x IOPS Gap [2026]
