Can I move from GameAnalytics, and how long does it take?
Yes. The two SDKs are separate, so one build can send to both. For a small game, our estimate is a day or two of code: one Track() call for each GameAnalytics event call. Then keep both SDKs for at least two weeks before you remove GameAnalytics. The two weeks are our advice, not a rule.
What carries over: your event calls (business, resource, progression, design and error events), your build and version labels, your own user ID, and your consent switch. Sessions and errors need no code, because our Unity and Godot SDKs send them for you.
What does not carry over: your history, A/B tests, remote configs, custom dimensions as a sticky setting, ad events for ad networks, and the FPS and memory health events. Manalens does not have these. The mapping table below marks each gap with "No".
The move has five steps. Each step has its own section below.
- Export what you want to keep from GameAnalytics, or keep the account open to read your history there.
- Install the Manalens SDK for your engine, next to the GameAnalytics SDK, and map each event call.
- Ship one build that sends to both tools, and run it for at least two weeks.
- Check that daily players, sessions and revenue move the same way in both tools, and explain each gap.
- Remove the GameAnalytics calls and the SDK, and ship a build without them.
Sources: GameAnalytics docs: Unity SDK and Godot SDK event tracking; GameAnalytics pricing; Manalens Unity SDK, Godot SDK and app events documentation; Manalens comparison page for GameAnalytics.
Why do studios move from GameAnalytics?
Most moves start with a need for data that GameAnalytics does not list: Steam wishlists and sales, store links, creator codes and revenue by marketing channel, next to the game events. Price is not a reason: GameAnalytics has a free plan with no MAU cap, and Manalens has no free plan.
Two smaller reasons come from the docs. Raw player data is on PipelineIQ only, which starts at $499 a month. And the GameAnalytics Godot SDK is a GDExtension that needs Godot 4.5 or later, while our Godot SDK is plain GDScript for Godot 4.
The table lists what GameAnalytics documents. It is not a full list of features.
| Topic | What GameAnalytics says |
|---|---|
| Free plan | Free, with no MAU cap and no credit card. |
| AnalyticsIQ Pro | $49 a month, billed monthly, with a 14-day free trial. |
| PipelineIQ | From $499 a month. Raw player data to your AWS or GCS bucket, a managed BigQuery warehouse and the Metrics API. |
| A/B testing and remote configs | Listed on every plan, the free plan too. |
| Unity SDK | Unity 2022.3 or later. |
| Godot SDK | Godot 4.5 or later. A GDExtension for iOS, Android, Web, Windows, macOS and Linux. |
| Ad events and health events | In the Unity SDK, ad events and health events (FPS, memory) are for iOS and Android only. |
| Custom dimensions | Three dimensions. The SDKs take up to 20 values for each. |
| Days in reports | Metrics are calculated in UTC days and hours. |
Sources: GameAnalytics pricing; GameAnalytics docs: Unity SDK (get started, event tracking, health), Godot SDK setup, Custom dimensions and Metrics; Manalens pricing and Godot SDK documentation.
How do GameAnalytics events map to Manalens?
Each GameAnalytics event type becomes one flat Track() call with properties, and sessions need no code. GameAnalytics has six event types with fixed fields: business, resource, progression, design, error and ad. Manalens has one call, Track(name, properties), and conventions for the names. Our event conventions follow the GameAnalytics event model, without its colon-joined IDs.
Five GameAnalytics features have no match: remote configs, A/B tests, ad revenue from ad networks, the FPS and memory health events, and store receipt validation. If your game reads remote configs or A/B test variants in code, keep GameAnalytics for that part, or move those values to another service first.
Use flat snake_case names, such as level_complete. Put the parts of a colon-joined ID in properties: the design event kill:boss:dragon becomes boss_kill with boss = "dragon".
| Concept | Manalens | GameAnalytics | Match |
|---|---|---|---|
| Business event (real money) | Track("purchase") with revenue (4.99, not 499) and currency | NewBusinessEvent(currency, amount in cents, itemType, itemId, cartType) | Close: send the amount in major units |
| Receipt validation | No | GAReceiptInfo for the App Store and Google Play | No |
| Resource event | Track("resource") with flow (source or sink), currency, amount and item | NewResourceEvent(flowType, currency, amount, itemType, itemId) | Close: no list of currencies to register first |
| Progression event | Track("level_start"), Track("level_complete") and Track("level_fail") with level, attempt and score | NewProgressionEvent(status, progression01, progression02, progression03, score) | Close: the three parts become properties |
| Design event | Track("name", properties) | NewDesignEvent("part1:part2:part3", value) | Close: the ID parts become properties |
| Error event | TrackError() with a severity of debug, info, warning, error or critical. Engine errors are captured for you. | NewErrorEvent(severity, message), with the same five severities | Direct |
| Ad event | No standard event. Send your own, such as Track("ad_impression"). | NewAdEvent(adAction, adType, adSdkName, adPlacement), on iOS and Android | Partial |
| Ad revenue from ad networks | No | Impression data from MAX, ironSource, AdMob and other networks | No |
| Session start and end | session_start and session_end with duration_s (automatic) | Automatic, with session length | Close: each tool has its own session rules |
| Manual session handling | No | StartSession() and EndSession() | No |
| First launch | game_open with is_first_open = true (automatic) | New users, counted the first time a user sends events | Close |
| User ID | A random anonymous ID for each install. Identify("player_42") joins devices and your website, at any time. | A default ID for each platform, or SetCustomId() before the SDK starts | Close |
| Build and version | Build and AppVersion options, sent on every event | Build, set in the settings or with configureBuild() | Direct |
| Custom dimensions | No sticky setting. Send the value as a property on each event, then filter or break down by it. | Three dimensions, set once and sent with every event | No direct match |
| Global custom fields | No | SetGlobalCustomEventFields(), read in the data warehouse or the raw export | No |
| Custom fields on one event | Properties on any event: strings, numbers, booleans or null | Up to 50 fields for each event, read in the data warehouse or the raw export | Direct, and properties show in reports |
| Remote configs | No | GetRemoteConfigsValueAsString(key, defaultValue) | No |
| A/B tests | No | GetABTestingId() and GetABTestingVariantId() | No |
| Health events (FPS, memory, boot time, hardware) | No. The SDK sends no hardware details. | Performance and SDK init events, on iOS and Android in the Unity SDK | No |
| Consent switch | ConsentRequired and SetConsent(true or false). The choice is saved. | SetEnabledEventSubmission(false). Sending is on by default. | Close |
| Raw data to your own warehouse | Not yet. CSV export, SQL Explorer and a REST API today. | Raw export to AWS or GCS, and BigQuery, on PipelineIQ | Not yet |
| Engines with an SDK | Unity (2021.3 or later), Godot 4 and the web. Other engines send events over HTTP. | Unity, Godot, Unreal, Roblox, GameMaker, Defold and more | Partial |
Sources: GameAnalytics docs: Unity SDK (event tracking, configuration, health, remote configurations, A/B testing), Godot SDK (event tracking, configuration) and Custom dimensions; Manalens Unity SDK, Godot SDK, app events and revenue documentation.
What does the same event look like in Unity?
Replace each GameAnalytics.New...Event() call with one Manalens.Track() call. The example sends a completed level, a spent resource and a purchase in both SDKs.
Note two differences. A GameAnalytics business event takes the amount in cents as an integer, so 499 is $4.99. Our Revenue metric sums a numeric revenue property in major units, so send 4.99. And GameAnalytics rejects a resource event when its currency or item type is not registered in the settings first. Our SDK has no list to register.
Property values in our SDK are strings, numbers, booleans or null. The SDK drops lists, dictionaries and objects and logs a warning.
C# (Unity): GameAnalytics, then Manalens
// GameAnalytics
using GameAnalyticsSDK;
GameAnalytics.NewProgressionEvent(GAProgressionStatus.Complete, "world01", "stage02", "level03", 1200);
GameAnalytics.NewResourceEvent(GAResourceFlowType.Sink, "gold", 50, "weapon", "sword");
GameAnalytics.NewBusinessEvent("USD", 499, "chest", "large_treasure_chest", "shop");
GameAnalytics.NewDesignEvent("kill:boss:dragon", 5000);
// Manalens
using System.Collections.Generic;
using ManalensSdk;
Manalens.Track("level_complete", new Dictionary<string, object> { ["world"] = "world01", ["stage"] = "stage02", ["level"] = 3, ["score"] = 1200 });
Manalens.Track("resource", new Dictionary<string, object> { ["flow"] = "sink", ["currency"] = "gold", ["amount"] = 50, ["item"] = "sword" });
Manalens.Track("purchase", new Dictionary<string, object> { ["revenue"] = 4.99, ["currency"] = "USD", ["item"] = "large_treasure_chest" });
Manalens.Track("boss_kill", new Dictionary<string, object> { ["boss"] = "dragon", ["value"] = 5000 });Sources: GameAnalytics docs: Unity SDK, event tracking and configuration; Manalens Unity SDK and revenue documentation.
What does the same event look like in Godot?
Replace each call on the GameAnalytics singleton with one Manalens.track() call. The GameAnalytics Godot SDK is a GDExtension that you reach with Engine.get_singleton("GameAnalytics"). Our SDK is an addon in plain GDScript that adds the Manalens autoload, so it needs no native code and no build step.
In GameAnalytics, custom fields go in the optional last argument as a JSON string under the key "fields". In our SDK, every property is a key in one dictionary.
GDScript (Godot): GameAnalytics, then Manalens
# GameAnalytics
var gameAnalytics = Engine.get_singleton("GameAnalytics")
gameAnalytics.addProgressionEventWithScore("complete", "world01", "stage02", "level03", 1200)
gameAnalytics.addResourceEvent("sink", "gold", 50, "weapon", "sword", {})
gameAnalytics.addBusinessEvent("USD", 499, "chest", "large_treasure_chest", "shop", {})
gameAnalytics.addDesignEventWithValue("kill:boss:dragon", 5000)
# Manalens
Manalens.track("level_complete", {"world": "world01", "stage": "stage02", "level": 3, "score": 1200})
Manalens.track("resource", {"flow": "sink", "currency": "gold", "amount": 50, "item": "sword"})
Manalens.track("purchase", {"revenue": 4.99, "currency": "USD", "item": "large_treasure_chest"})
Manalens.track("boss_kill", {"boss": "dragon", "value": 5000})Sources: GameAnalytics docs: Godot SDK, setup and event tracking; Manalens Godot SDK documentation.
How do I install the SDK for my engine?
Use the Unity package or the Godot addon. For any other engine, send events to the HTTP endpoint. Install the new SDK next to GameAnalytics, and do not remove GameAnalytics yet.
Manalens has fewer SDKs than GameAnalytics. If your game runs on Roblox, or you do not want to write HTTP calls in Unreal, GameMaker or Defold, that is a reason to stay.
- Unity (2021.3 or later): during early access, ask for the package on the contact page and add it in the Package Manager from a folder or a .tgz file, then call Manalens.Init() once in the Awake() of a component in your first scene.
- Godot 4: copy the addons/manalens folder into your project, enable the plugin, then call Manalens.init() in _ready().
- Unreal Engine and other engines: there is no SDK. Send the same events as JSON to the events endpoint with your Publishable key.
- Web games: use the web SDK with the app option, so the game and your website share one player.
- Install game analytics in Unity →
- How to add analytics to a Godot game →
- How to add analytics to an Unreal Engine game →
- Engine analytics compared: Unreal, Godot, GameMaker, Construct, Phaser →
Sources: Manalens Unity SDK, Godot SDK and app events documentation; GameAnalytics docs: Unity SDK and Godot SDK setup.
How do I move start-up, user IDs and consent?
Start our SDK once at launch with the Publishable key from your project settings; it is safe to ship in a build. Set Enabled = !Application.isEditor in Unity, or "enabled": not OS.has_feature("editor") in Godot, so that editor runs do not mix test data into your reports.
For user IDs, GameAnalytics uses a default ID for each platform. You can replace it with SetCustomId() in Unity or configureUserId() in Godot, but only before the SDK starts. Our SDK keeps a random anonymous ID for each install. Call Identify() with your own player ID at any time, for example after sign-in, to join devices and your website to one player.
For consent, GameAnalytics sends events by default, and SetEnabledEventSubmission(false) turns sending off. With ConsentRequired = true, our SDK records nothing and writes no ID until SetConsent(true), and it saves the choice for the next launch. SetConsent(false) deletes the ID, the session and the queue on the device. During the move, call both from one consent handler.
C# (Unity)
// One consent handler for both SDKs during the move.
public void OnAnalyticsConsent(bool granted)
{
GameAnalytics.SetEnabledEventSubmission(granted);
Manalens.SetConsent(granted); // the choice is saved for the next launch
}
// GameAnalytics start-up: the keys are on the Settings object.
GameAnalytics.SetCustomId("player_42"); // only before Initialize()
GameAnalytics.Initialize();
// Manalens start-up
Manalens.Init(new ManalensOptions
{
PublishableKey = "YOUR_PUBLISHABLE_KEY",
Endpoint = "https://YOUR_COLLECTOR_ENDPOINT",
Storefront = "steam",
ConsentRequired = true,
Enabled = !Application.isEditor,
});
Manalens.Identify("player_42"); // at any timeSources: GameAnalytics docs: Unity SDK (get started, configuration) and Godot SDK configuration; Manalens Unity SDK and Godot SDK documentation.
What happens to my GameAnalytics history, and what can I export?
Your history does not move. Manalens has no import for GameAnalytics data, so new reports start on the day the new SDK ships. Export what you want to keep, or keep your GameAnalytics account open and read the old months there.
GameAnalytics documents two kinds of export. In Explore, a table of results downloads as a CSV file, with a comma, semicolon, colon or tab as the delimiter. The Explore page does not say which plan it needs, so check your own account. Raw, player-level data is on PipelineIQ only, which starts at $499 a month: Data Export to your AWS or GCS bucket, a managed BigQuery warehouse and the Metrics API.
How long GameAnalytics keeps your history is not on the pricing page. The FAQ says that you can export your data at any time, and that data is kept according to the terms of service and privacy policy. Read those terms for your plan, and export early if a date matters to you.
Keep the exports next to your new data. Our dashboards export each chart to CSV, so you can put old and new months side by side in a spreadsheet. Note the date you switched, and compare trends, not totals, across that date.
A backfill is possible but limited. Our server events API accepts past timestamps for backfills with the project secret key, from your own script. Those events count as events and revenue, but without a session they do not rebuild sessions or retention.
| What | How | Plan |
|---|---|---|
| Report results | Explore table export to CSV | Not stated on the Explore page: check your account |
| Raw player-level events | Data Export to an AWS or GCS bucket | PipelineIQ, from $499 a month |
| Player and session data for SQL | Managed BigQuery warehouse | PipelineIQ, from $499 a month |
| Aggregated metrics | Metrics API | PipelineIQ, from $499 a month |
Sources: GameAnalytics docs: Explore; GameAnalytics pricing and FAQ; Manalens dashboards and server events documentation.
How do I run both tools side by side?
Ship one build that sends every event to both tools, and keep it for at least two weeks. Two weeks give you two of each weekday to compare. The two SDKs are separate packages with separate IDs and separate queues, so they do not interfere. The GameAnalytics FAQ also says that most studios run it next to other tools.
The easiest way is one small wrapper function for each event in your game. The wrapper calls GameAnalytics and Manalens. At the end of the move, you delete one line in each wrapper.
Do not start on the day of a launch, a sale or a major update. Start a few weeks before, so that the new tool has a baseline before the big day.
- Sends: the GameAnalytics Unity SDK sends its event queue every 8 seconds. Our SDK sends every 10 seconds, at 20 queued events, on pause and on quit.
- Offline play: our SDK saves events on disk and sends them later with their original time. The collector accepts app events up to 7 days old.
- Errors: the GameAnalytics Unity SDK sends at most 10 automatic error events after launch. Our SDK sends at most 50 captured errors in one session, and app_unclean_exit after a crash.
- Web builds: our collector accepts a web build from your project domain and from itch.io by default. Add other portals to the allowed origins first.
Sources: GameAnalytics FAQ; GameAnalytics docs: Unity SDK configuration; Manalens Unity SDK and Godot SDK documentation.
Why is DAU different in the two tools?
Expect DAU to be lower in Manalens at first, and expect a small gap to stay. Both tools count distinct players in a UTC day, but they do not see the same players and they do not use the same ID. GameAnalytics defines DAU as the unique user count reported per day. On our Game KPIs dashboard, a player is one install, and only events that the game sends count.
Compare trends, not totals. If the two lines rise and fall on the same days, and the gap is steady, the new numbers are right. A gap that grows or jumps needs a look.
Retention can differ too. GameAnalytics uses strict retention: a player counts on day N only when they return on that exact day. Our retention report has two modes. Rolling is the default for new charts and counts a return on day N or later. Choose Recurring to compare with GameAnalytics.
- Old builds: players on a build from before the move send to GameAnalytics only. This is the largest gap in the first weeks, and it shrinks as players update.
- User IDs: GameAnalytics counts its own user IDs, or your custom ID. We count a random ID for each install, so a reinstall is a new player until you call Identify().
- Consent: with ConsentRequired, our SDK sends nothing before the player agrees. GameAnalytics sends by default.
- Editor and test runs: with Enabled = !Application.isEditor, your own test sessions are in one tool and not in the other.
- Late events: our collector refuses app events older than 7 days, so a player who was offline for longer is not counted for those days.
- Sessions: GameAnalytics counts session start events. Our SDK ends a session after 30 minutes without focus or events, and after 24 hours.
Sources: GameAnalytics docs: Metrics, Unity SDK configuration; Manalens metrics, retention, Unity SDK and Godot SDK documentation.
What should I test before I remove GameAnalytics?
Test a development build, not the editor, and check each item below in the activity feed. Set Debug = true (debug in Godot) to log each queued event and each failed send.
Remove GameAnalytics last. Delete every GameAnalytics call, the GameAnalytics object in your first Unity scene or the Godot plugin, and the package or addon folder. Then ship a build without them. If your game reads remote configs or A/B test variants, replace those reads with fixed values or another service first, or the game loses them.
- game_open and session_start arrive on the first launch, with is_first_open = true.
- Each mapped event arrives with the right name and properties, and no property is dropped with a warning.
- A purchase arrives once, with revenue in major units (4.99, not 499) and a currency.
- With ConsentRequired, nothing is sent before SetConsent(true), and your consent handler stops both SDKs.
- Identify() with the same player ID joins the player on a second device and on your website.
- Play offline, then go online: the queued events arrive with their original time.
- Quit the game: session_end arrives with duration_s.
- Daily players, sessions and revenue in both tools move the same way for at least two weeks.
- No code reads a remote config or an A/B test variant from GameAnalytics any more.
Sources: Manalens Unity SDK and Godot SDK documentation; GameAnalytics docs: Unity SDK, get started and remote configurations.
When should I stay on GameAnalytics?
Stay if the free plan does what you need. GameAnalytics is free with no MAU cap, and Manalens is a paid tool with a trial. If you only study gameplay, a move costs money and gives you little.
You can also keep both. Keep GameAnalytics for A/B tests and remote configs, and use Manalens for Steam data and marketing attribution. Each tool counts its own players, so the totals can differ.
- You use A/B tests or remote configs. GameAnalytics lists both on every plan. Manalens has neither.
- Your game is a mobile free-to-play game with ads. GameAnalytics has ad events and ad revenue from ad networks. We have no standard ad event and no ad network data.
- Your game runs on Unreal, Roblox, GameMaker, Defold or another engine where we have no SDK, and you do not want to write HTTP calls.
- You need FPS, memory and boot time data, or raw player data in BigQuery or your own bucket. We have no health events, and warehouse export is planned but not ready.
- You need store receipt validation for the App Store or Google Play.
- You do not sell on Steam or itch.io, and you do not need marketing attribution. Then our main strength does not help you.
- Manalens vs GameAnalytics →
- 6 GameAnalytics alternatives for indie game studios →
- How to move from Unity Analytics to Manalens →
Sources: GameAnalytics pricing; GameAnalytics docs: Unity SDK (event tracking, health, remote configurations, A/B testing); Manalens pricing and comparison page for GameAnalytics.
How do I start the move?
Manalens is the analytics and growth engine built for games. Install the Unity or Godot SDK next to GameAnalytics, map your events, and see your players next to Steam wishlists, sales and the channels that brought them.
Sources: Manalens product documentation.
Frequently asked questions
Can I import my GameAnalytics history into Manalens?
No. There is no import for GameAnalytics data. Export report tables to CSV from Explore, or raw data with PipelineIQ, which starts at $499 a month, or keep the account open to read old months. Our server events API accepts past timestamps for a backfill, but it does not rebuild sessions or retention.
Can I run GameAnalytics and Manalens together?
Yes. They are separate SDKs with separate IDs and queues, so one build can send to both. Run them together for at least two weeks and compare trends, not totals. You can also keep both for good: GameAnalytics for A/B tests and remote configs, Manalens for Steam data and marketing attribution.
How long does a move from GameAnalytics take?
Our estimate for a small game is a day or two of code, because each GameAnalytics event call becomes one Track() call. Then run both SDKs in one build for at least two weeks before you remove GameAnalytics. A game that reads remote configs or A/B test variants needs more time to replace them.
Why is DAU lower in Manalens than in GameAnalytics?
Mostly because players on old builds send to GameAnalytics only, so the gap shrinks as players update. The two tools also use different user IDs, and with ConsentRequired our SDK sends nothing before the player agrees. Both tools count in UTC days. Compare the trend of the two lines, not the totals.
Does Manalens have A/B tests and remote configs?
No. GameAnalytics lists A/B testing and remote configs on every plan, the free plan too, so stay with GameAnalytics if you depend on them. Manalens fits a different job: Steam wishlists and sales, store links, creator codes and revenue by channel, next to your game events.
Do I need to register currencies, item types or dimensions first?
Not in Manalens. You call Track() with a name and properties, and the event appears in reports. In GameAnalytics, resource currencies and item types must be registered before the SDK starts, at most 20 of each, and custom dimension values must be defined first. Values that are not defined are ignored.
Sources and implementation
- GameAnalytics: Pricing (read 19 November 2026) ↗
- GameAnalytics: Frequently asked questions (read 19 November 2026) ↗
- GameAnalytics docs: Unity SDK, get started (read 19 November 2026) ↗
- GameAnalytics docs: Unity SDK, configuration (read 19 November 2026) ↗
- GameAnalytics docs: Unity SDK, event tracking (read 19 November 2026) ↗
- GameAnalytics docs: Unity SDK, health (read 19 November 2026) ↗
- GameAnalytics docs: Unity SDK, remote configurations (read 19 November 2026) ↗
- GameAnalytics docs: Unity SDK, A/B testing (read 19 November 2026) ↗
- GameAnalytics docs: Godot SDK, setup (read 19 November 2026) ↗
- GameAnalytics docs: Godot SDK, configuration (read 19 November 2026) ↗
- GameAnalytics docs: Godot SDK, event tracking (read 19 November 2026) ↗
- GameAnalytics docs: Godot SDK, remote configurations (read 19 November 2026) ↗
- GameAnalytics docs: Godot SDK, A/B testing (read 19 November 2026) ↗
- GameAnalytics docs: Custom dimensions (read 19 November 2026) ↗
- GameAnalytics docs: Metrics (read 19 November 2026) ↗
- GameAnalytics docs: Explore (read 19 November 2026) ↗