Game-analytics implementation · 2026
What Game-Analytics Implementation Work Remains Worth Paying For?
Event governance and warehouse handoff remain sellable; basic tracking and dashboards do not.
The report separates installing a free analytics kit from defining stable events, checking their quality, modelling warehouse data and keeping several games comparable.
- Platform sample
- 5 current analytics and warehouse routes.
- Commercial evidence
- 4 public price families and direct consulting offers.
- Customer evidence
- 20+ logos, 9 detailed cases and a named consulting purchase.
- Market
- Software, consulting and data operations are purchased.
- Best bounded job
- Event governance, quality checks and warehouse handoff.
- No-Go
- Stand-alone SDK installation or generic dashboards.
Brief mode keeps the findings, prices, segment comparison and final answer.
Research context
- Background: Major game-analytics tools make basic tracking and dashboards free or inexpensive, while studios still struggle with inconsistent events, duplicated data and cross-title comparisons.
- Answer sought: Which implementation and analysis work is still purchased, what can be accepted as a bounded deliverable, and which parts have become too commoditised to enter?
- Main sources: Five current platform routes, four public price families, direct consulting offers, named customer cases and official data-sharing/warehouse documentation.
In plain language: what does the customer buy?
A game records actions such as starting a level, spending currency, seeing an offer or leaving a tutorial. Installing an analytics kit is easy; deciding exactly what each event means, preventing duplicates, keeping names stable after every release, joining data from several games, and turning it into decisions are not.
The customer buys a reliable measurement system: an event dictionary tied to business questions, automatic checks, a warehouse-ready data model, agreed dashboards, documentation and scheduled reviews after releases. The deliverable is not “more charts”; it is confidence that two people reading the same number reach the same conclusion.
Scope and sample
- Five current routes: GameAnalytics, Unity Analytics, devtodev, Microsoft PlayFab, and a Firebase/BigQuery-style stack.
- Six overlapping jobs: basic SDK tracking, event governance and quality audit, dashboards/funnels/retention, warehouse and business-intelligence handoff, economy/monetisation analysis, and continuing multi-title operations.
- Commercial evidence: four major routes have a free or US$0 entry; GameAnalytics and devtodev publish paid data/support tiers; Unity sells game-data consulting directly.
- Case evidence: GameAnalytics displays at least 20 named studio/publisher logos and nine detailed customer stories; devtodev shows more than ten named testimonials, including a studio that explicitly bought consulting.
Vendor-selected customers are evidence of adoption and purchased tasks, not market share or representative outcomes. One company appearing across several pages is counted once when describing buyer evidence.
Findings at a glance
- [Observation] Basic analytics is heavily commoditised. GameAnalytics has a no-MAU-limit free tier, Unity includes 50,000 monthly active users free, devtodev includes 25,000, and PlayFab starts at US$0 usage-based pricing.
- [Observation] Clean data access commands a much higher platform price. GameAnalytics lists AnalyticsIQ at US$49/month and PipelineIQ, its raw-data pipeline, from US$499/month—a 10.18× difference between unlike but adjacent tiers.
- [Observation] Advice and implementation are already sold. Unity explicitly offers work on player KPIs, monetisation and retention; Tiramisu says it bought devtodev consulting and used the reports to change its economy and find bottlenecks and bugs.
- [Observation] Multi-game consistency is a documented paid problem. TapNation reports fragmented tracking, duplicate data and metrics that were not comparable across games before adopting common templates and PipelineIQ.
- [Observation] An outside operator has a supported route to the data. GameAnalytics Data Sharing lets a studio share game data with a publisher or agency; the recipient needs PipelineIQ.
- [Inference] The enterable work sits between product design and data engineering. A small supplier can define meanings, test collection and hand off a usable model; it should not compete with free dashboards or promise revenue uplift.
Who pays, and what triggers the project?
| Buyer | Trigger | Purchased result |
|---|---|---|
| Small studio approaching launch or live operation | No shared definition of activation, retention or economy events | Event dictionary, implementation plan and automated validation |
| Publisher onboarding several partner studios | Every game names and calculates the same metric differently | Common template, mapping rules and comparable portfolio view |
| Growing live-game team | Spreadsheet exports and ad-hoc queries no longer reconcile | Warehouse model, scheduled pipeline and documented dashboard |
| Studio changing analytics tools | Historical events, identities and versions do not line up | Dual-run audit, migration mapping and acceptance tests |
| Product or economy lead without a data engineer | Knows the questions but cannot maintain SQL and data quality | Bounded analysis pack and release-by-release review |
The named cases include mobile studios and publishers with one game through multi-title portfolios. Public pages do not provide a complete team-size, country or genre distribution, so those dimensions cannot be used to estimate an addressable market.
Current prices show where value has moved
| Route | Current public entry | Higher paid boundary relevant to implementation |
|---|---|---|
| GameAnalytics | Core analytics free, without an MAU cap | AnalyticsIQ US$49/month; PipelineIQ from US$499/month; MarketIQ US$499/month |
| Unity Analytics | First 50,000 MAU free | From US$0.00360 per MAU above the free allowance, with lower rates at larger tiers |
| devtodev | First 25,000 MAU free | Basic starts at US$33 per 10,000 MAU; page calculates 100,000 MAU at US$415/month |
| Microsoft PlayFab | US$0 usage-based start | Standard US$99/month; Premium US$1,999; Enterprise from US$10,000 |
| BigQuery queried through GameAnalytics | Storage/export product required | US$6.25 per TiB queried, before the surrounding pipeline and modelling work |
At 100,000 MAU, Unity's published formula gives US$180/month: (100,000−50,000)×US$0.00360. devtodev's page gives US$415/month, or 2.31× the Unity figure, but retention, features and service differ.
PlayFab Premium is 20.19× Standard. PlayFab also includes broader game-backend services, so this ratio must not be presented as the value of analytics alone. Likewise, platform subscriptions are not prices for an independent implementation project.
Direct evidence that studios pay beyond basic dashboards
| Source | Observed problem and purchased work | Decision relevance | Caveat |
|---|---|---|---|
| Tiramisu / devtodev | Studio explicitly used consultancy; reports informed economy changes and exposed bottlenecks and small bugs | Analysis itself is purchased, not only software access | Customer/vendor account; no price or isolated causal effect |
| TapNation / GameAnalytics | Fragmented tracking, duplicate data and non-comparable games led to common templates and PipelineIQ; 19 games are cited | Multi-title governance and pipeline work have a concrete buyer | Reported 50% LTV gain over six months involved other tools too |
| GameAnalytics Data Sharing | Studios can give a publisher or agency governed access; recipient needs PipelineIQ | A practical delivery path exists for an external analyst or publisher | Feature availability does not measure independent-service demand |
| Unity game consulting | Unity sells KPI, monetisation, retention and ongoing game-data consulting | Professional help is an established product category | No public rate card or win-rate denominator |
| GameAnalytics Data Warehouse customers | Customers describe SQL work and reducing the need for another data engineer | Warehouse modelling can replace recurring manual work | Selected testimonials, not a labour-market study |
The counterexample is equally important: custom events, dashboards, funnels, retention, experiments and remote configuration are available free or cheaply across major tools. A supplier cannot treat ordinary charts as scarce output.
Six jobs compared
| Segment | Demand evidence | Competition and substitutes | Entry judgment |
|---|---|---|---|
| Basic SDK and event installation | Every platform requires integration | Four routes have a free/US$0 start, strong docs and AI coding help | No-Go as a stand-alone service |
| Event definitions and quality audit | TapNation's duplicates and non-comparable data; every platform accepts custom events | Templates help, but cannot decide game-specific meanings | Best initial, testable deliverable |
| Dashboards, funnels and retention | Used in every listed platform | Core builders and standard views are free or inexpensive | Bundle only as acceptance output |
| Warehouse, export and BI handoff | PipelineIQ starts at US$499; warehouse cases require SQL and modelling | Platforms handle plumbing but not the studio's semantic model | Strong when paired with governance |
| Economy and monetisation analysis | Unity sells it; Tiramisu bought it | Needs game-design and statistical judgement; attribution is hard | Valuable add-on, never guarantee uplift |
| Multi-title continuing operations | TapNation covers 19 games; Data Sharing supports publishers/agencies | Publishers and internal analytics teams compete | Best recurrence trigger after a successful setup |
The smallest sellable implementation
The evidence supports this bounded package:
A business-question workshop; event and property dictionary with owners and version rules; instrumented sample flow; automated checks for missing, duplicate and invalid events; a cross-title metric layer; warehouse/BI handoff; one acceptance dashboard; and two post-release reviews.
Acceptance is observable: a fixed test script produces the expected event sequence; duplicates and required fields are checked; identities and versions reconcile; a named metric returns the same result in source, warehouse and dashboard; documentation lets the studio add one new event without the supplier.
For recurring work, sell scheduled release audits and portfolio metric maintenance with explicit response hours. Do not accept vague responsibility for “improving retention,” and do not become an unbounded on-call data team.
Risks, stop conditions and evidence gaps
| Issue | Effect | Boundary or stop condition |
|---|---|---|
| Free tools and AI-assisted coding | Basic installation has little pricing power | Stop if the buyer only wants an SDK and standard dashboard |
| Weak business questions | Perfect events still produce unused data | Do not begin until the buyer names decisions, owners and release dates |
| Privacy and platform policy | Player identifiers and cross-region data create obligations | Minimise personal data and require the customer to own consent/legal decisions |
| Outcome attribution | Revenue or retention changes have many causes | Promise verified data and analysis, not growth |
| Missing market economics | Independent contract values, hours, win rates and failure rates are private | Platform price and customer results are not service profit |
Final answer
Studios do pay for more than analytics software. Current consulting offers, a named consulting purchase, paid raw-data tiers, multi-game cases and an agency data-sharing route establish the category.
The enterable unit is event governance plus a warehouse-ready handoff, not “analytics setup.” The strongest buyer is a publisher or studio that has releases to compare, data inconsistencies to fix and no spare data engineer.
Basic SDK installation and generic dashboards are No-Go. They are bundled into free products and increasingly assisted by AI. A viable offer must make definitions stable, data testable and several games comparable, while keeping business outcomes outside the guarantee.
Direct sources
- GameAnalytics pricing (accessed 2026-08-27)
- GameAnalytics customers (accessed 2026-08-27)
- TapNation customer case (accessed 2026-08-27)
- GameAnalytics Data Warehouse (accessed 2026-08-27)
- GameAnalytics Data Sharing documentation (accessed 2026-08-27)
- Unity Analytics pricing and billing (accessed 2026-08-27)
- Unity Gaming Services pricing (accessed 2026-08-27)
- Unity game consulting (accessed 2026-08-27)
- devtodev pricing (accessed 2026-08-27)
- devtodev consulting and Tiramisu account (accessed 2026-08-27)
- Microsoft PlayFab pricing (accessed 2026-08-27)
Completeness note: The report compares five current platform routes and six jobs, using four public price families, at least 20 named customer logos, nine detailed GameAnalytics cases, more than ten devtodev testimonials and one explicit consulting purchase. It supports a product-scope and entry-boundary decision—not the number of addressable buyers, typical contract value, acquisition cost, hours or profit.