Who should move from Unity Analytics, and when?

Move if your game still calls Legacy Analytics, if your organization lost access, or if you need Steam wishlists, sales and marketing data next to your game events. Stay if you are under 50,000 MAU and use A/B Testing or Remote Config. Unity Analytics is free to that limit, and Manalens has no A/B tests or remote config.

Pick a quiet time. Our advice is to start the move a few weeks before a launch, a sale or a major update, so that the new tool has a baseline before the big day. Do not switch on the day of a launch: you lose the comparison that tells you the new numbers are right.

The move has four steps. Each step has its own section below.

  1. Export what you want to keep from Unity Analytics: dashboard reports as CSV, and raw data through Data Access if you need it.
  2. Map each Unity standard event and custom event to a Manalens event name and its properties.
  3. Install the Manalens Unity SDK next to Unity Analytics, and ship a build that sends to both.
  4. Compare trends in the two tools for at least two weeks, then remove the Unity Analytics calls and package.

Sources: Unity Support (updated 21 October 2026 and 9 October 2026); Unity Analytics docs, Pricing; Manalens comparison page for Unity Analytics.

Why do studios move from Unity Analytics?

Most moves start with one of three things: a shutdown notice, a price step above 50,000 MAU, or a need for data that Unity Analytics does not list, such as Steam wishlists and sales. The table lists what Unity documents. It is not a full list of features.

Unity says that Legacy Analytics was switched off on 2 February 2024, and that games must move to the current Unity Analytics SDK to collect data again. Unity Support also says that, since 30 June 2026, organizations registered in mainland China, Hong Kong or Macau can no longer use most Unity global Gaming Services, Analytics included. Their requests fail with HTTP 451. The rule depends on where the organization is registered, not where the players are. Unity points these studios to its China-based services, and says it has no automated migration tooling between the two.

If your organization is registered in one of those regions, check that any new tool is available to you, ours included, before you plan the move.

What Unity documents about Unity Analytics, read 18 November 2026 and checked again 19 November 2026.
TopicWhat Unity says
Legacy AnalyticsSwitched off on 2 February 2024. Move to the current SDK to collect data again.
Mainland China, Hong Kong, MacauSince 30 June 2026, organizations registered there can no longer use Analytics. Unity Ads, In-App Purchasing and Authentication are still available.
Free tierUp to 50,000 MAU.
Price above the free tier$0.00360 per MAU from 50,001 to 150,000, then lower rates per tier. Contact Unity above 5,000,000 MAU.
How MAU is countedUnique user IDs with a session in the month, across all projects and environments in your organization.
Custom eventsAbove the free tier, a fair use limit of 500 custom events per MAU. Valid and invalid events both count.
SQL Data ExplorerRead-only SQL on your Analytics data, billed by query seconds. The free tier includes 0.05 query seconds per MAU, and the same figure is a fair use limit above it.
Raw event dataKept for 13 months, then deleted. It cannot be retrieved after that.
PlatformsThe Get started page lists iOS, Android, Windows, macOS and WebGL. The FAQ also lists Linux.
Unity versionUnity 2022.3 or later since SDK 6.2.0 (4 December 2025). The Get started page still says 2021.3. The latest SDK is 6.3.0, from March 2026.

Sources: Unity Support (updated 21 October 2026 and 9 October 2026); Unity Analytics docs: Pricing, MAU-based pricing, Fair usage limits, Get started, FAQ and SQL Data Explorer; Unity Analytics SDK changelog.

How do Unity Analytics events map to Manalens?

Most Unity events have a close match, and our SDK sends the session events for you. Unity sends sdkStart, newPlayer, gameStarted, clientDevice, gameRunning and gameEnded automatically. Our SDK sends game_open, session_start, session_end, errors and app_unclean_exit automatically. You record purchases, ads and your own game events in code on both sides.

Three Unity events have no direct match. We have no heartbeat event like gameRunning, because a session ends after 30 minutes without focus or events. We do not take channel data from mobile attribution partners, which is what acquisitionSource holds. And there is no standard ad event, so send your own.

Use flat snake_case names, such as level_complete. Our event conventions follow the GameAnalytics event model, so reports and funnels line up across games.

Unity Analytics events and their nearest Manalens event. Unity events from the Unity Analytics docs, read 18 November 2026.
Unity AnalyticsManalensMatch
sdkStart, gameStarted (automatic, at session start)session_start and game_open (automatic)Close
newPlayer (automatic, when the user ID differs from the last session)game_open with is_first_open = true (automatic, first launch on the device)Partial: a new user ID does not make a new player
clientDevice (automatic, at session start)context.app on every event: platform, app_version, build, storefrontPartial: we send no device or hardware details
gameRunning (every 60 seconds with no other events)NoneNo direct match
gameEnded (automatic, at exit)session_end with duration_s (automatic)Close
transaction (manual, or sent by Unity IAP 4.2 or higher)Track("purchase") with revenue and currencyPartial: flat properties, no item arrays
transactionFailed (manual)Track("purchase_failed") as your own eventNo standard event
adImpression (manual)Track("ad_impression") as your own eventNo standard event
acquisitionSource (manual, from an attribution partner SDK)Install attribution, LinkUrl() and the Steam UTM importNo direct match
Custom events (Event Manager schema and an Event class)Track("name", properties)Direct, with no schema to create first
External user ID (UnityServices.ExternalUserId)Identify("player_42")Close
RequestDataDeletion() and ddnaForgetMeSetConsent(false) on the device; contact support to delete sent dataPartial

Sources: Unity Analytics docs: Standard events, Record an event, Record events with a custom user ID, acquisitionSource event; Manalens Unity SDK and app events documentation.

How do I move a custom event?

Replace each RecordEvent() call with one Track() call. In Unity Analytics, you first create the event and its parameters in the Event Manager, then write a matching Event class, because events that do not match a schema on the dashboard are rejected. In Manalens, you send the name and a dictionary of properties. There is no schema to create first.

Property values in our SDK are strings, numbers, booleans or null. Unity also takes DateTime values from SDK 6.2.0. Send a date as an ISO 8601 string instead. Our SDK drops lists, dictionaries and objects and logs a warning.

C#: Unity Analytics, then Manalens

// Unity Analytics: create levelComplete in the Event Manager first.
public class LevelCompleteEvent : Unity.Services.Analytics.Event
{
    public LevelCompleteEvent() : base("levelComplete") { }
    public int Level { set { SetParameter("level", value); } }
    public int Score { set { SetParameter("score", value); } }
}

AnalyticsService.Instance.RecordEvent(new LevelCompleteEvent { Level = 3, Score = 1200 });

// Manalens: no schema to create first.
Manalens.Track("level_complete", new Dictionary<string, object> { ["level"] = 3, ["score"] = 1200 });

Sources: Unity Analytics docs: Create a custom event and Record an event; Manalens Unity SDK documentation.

How do I move purchases?

Send one purchase event with a numeric revenue property. The Revenue metric sums that property. Unity's transaction event has arrays for items and currencies received and spent. Our events are flat, so send one event per purchase and put the item name in a property.

Watch for double counts. Unity IAP 4.2 or higher sends transaction events to Unity Analytics for you, and Unity warns that sending them manually as well counts them twice. Our SDK does not read Unity IAP, so you send the purchase yourself. If you also connect Stripe or Paddle, the provider record wins for that player, so a sale is counted once.

C#: Unity Analytics, then Manalens

// Unity Analytics (Unity's example, shortened)
TransactionEvent transaction = new TransactionEvent
{
    TransactionId = "100000576198248",
    TransactionName = "IAP - A Large Treasure Chest",
    TransactionType = TransactionType.PURCHASE,
    TransactionServer = TransactionServer.APPLE,
};
transaction.SpentRealCurrency = new TransactionRealCurrency
{
    RealCurrencyType = "USD",
    RealCurrencyAmount = AnalyticsService.Instance.ConvertCurrencyToMinorUnits("USD", 4.99)
};
AnalyticsService.Instance.RecordEvent(transaction);

// Manalens
Manalens.Track("purchase", new Dictionary<string, object>
{
    ["revenue"] = 4.99, ["currency"] = "USD", ["store"] = "app_store", ["item"] = "large_treasure_chest",
});

Sources: Unity Analytics docs: Record transaction events; Manalens revenue documentation.

What happens to my old Unity Analytics data?

Your history does not move. There is no import for Unity Analytics data, so new reports start on the day the new SDK ships. Export what you want to keep before you switch off Unity Analytics.

Unity documents two exports. Dashboard reports export to PNG or CSV. For raw data, Data Access shares your organization's Analytics data through Snowflake. You need your own Snowflake account in GCP EU-WEST4 or US-CENTRAL1, and only organization owners can open the Data Access settings. Unity keeps raw event data for 13 months and then deletes it, so export early. While you still have access, SQL Data Explorer runs read-only SQL on the same data, so you can note the totals you want to compare with later.

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.

Sources: Unity Analytics docs: FAQ, Data Access and SQL Data Explorer; Manalens dashboards and server events documentation.

How do I run both SDKs during the move?

Ship one build that sends to both tools, and keep it for at least two weeks. That is our advice, not a rule: two weeks give you two of each weekday to compare. The two SDKs are separate packages with separate IDs, so they do not interfere.

Expect the totals to differ. Unity counts MAU as unique user IDs with a session, across all projects and environments in your organization. We count distinct players with at least one event in a calendar month, per project. Sessions also differ, because each tool starts and ends a session by its own rules.

  • Sends: Unity uploads events every 60 seconds. Our SDK sends every 10 seconds, at 20 queued events, on pause and on quit.
  • Offline play: both SDKs cache events on the device. Unity rejects events collected more than 30 days before they arrive. Our collector accepts app events up to 7 days old.
  • Platforms: Unity lists iOS, Android, Windows, macOS and WebGL on its Get started page, and its FAQ adds Linux. Our SDK runs on Windows, macOS, Linux, Android, iOS and WebGL, so Steam Deck builds work too.
  • Errors: our SDK also sends exceptions, Debug.LogError and failed asserts as error events, and app_unclean_exit after a crash.

Sources: Unity Analytics docs: MAU-based pricing, Record an event and FAQ; Manalens pricing and Unity SDK documentation.

What should I test before I remove Unity Analytics?

Test a development build, not the editor, and check each item below in the activity feed. Set Debug = true to log each queued event and each failed send.

  • 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 and currency, and is not counted twice with a provider record.
  • With ConsentRequired, nothing is sent before SetConsent(true), and SetConsent(false) 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 and sessions in both tools move the same way for at least two weeks.
  • After the switch, remove every AnalyticsService call and the Analytics package, and ship a build without them.

Sources: Manalens Unity SDK documentation; Unity Analytics docs: Record transaction events.

How do I start the move?

Manalens is the analytics and growth engine built for games. Install the Unity SDK next to Unity Analytics, 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

Is Unity Analytics shutting down?

Not for everyone. The current Unity Analytics is part of Unity Gaming Services and is free for the first 50,000 MAU. Unity switched off Legacy Analytics on 2 February 2024. Since 30 June 2026, organizations registered in mainland China, Hong Kong or Macau can no longer use Analytics, Unity Support says.

Can I import my Unity Analytics history?

No. There is no import for Unity Analytics data. Export dashboard reports to CSV, or raw data through Data Access, before you switch. Unity keeps raw event data for 13 months. Our server events API accepts past timestamps for a backfill, but it does not rebuild sessions or retention.

Can I run Unity Analytics and Manalens together?

Yes. They are separate packages with separate IDs, so one build can send to both. Run them together for at least two weeks and compare trends, not totals. Each tool counts players and sessions in its own way, and Unity counts MAU across all projects and environments in your organization.

Do I need to create events in a dashboard first?

Not in Manalens. You call Track() with a name and a dictionary of properties, and the event appears in reports. In Unity Analytics, you create a custom event and its parameters in the Event Manager first, and events that do not match a schema on the dashboard are rejected.

Does Manalens have A/B tests and remote config?

No. Unity A/B Testing and Remote Config are free in Unity Gaming Services, so stay with Unity Analytics 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.

Sources and implementation