Migrate from Unity Analytics

Moving from Unity Analytics (UGS Analytics) to PlayGenus takes three steps: export your event data from the Unity Dashboard, upload it to the PlayGenus importer, and review the event mapping we propose. Once confirmed, your history is ingested and the churn, LTV, and forecast models train on your real players — predictions with context, not a cold start.

The general import mechanics — file limits, the mapping review UI, multi-file imports — live in Import your historical data. This page covers the Unity-specific parts.

Step 1 — Export your events from Unity

1. In the Unity Dashboard, go to Analytics → Data Export.
2. Set the date range and request the export.
3. Download the TSV file when it's ready.

The importer takes Unity's TSV directly — no reformatting needed. If your setup exports elsewhere (some studios pipe UGS data into their own warehouse), any CSV, TSV, JSON, or NDJSON dump of events works; the import guide lists the three columns any custom file needs. Bring as much history as you have — 90 days is a sensible minimum, and more span means better predictions.

Step 2 — Upload to PlayGenus

Historical Imports → New import, pick Unity Analytics as the source format, and drop the file in. Import maps your old events onto your approved tracking plan, so the plan has to exist first — see How onboarding works if you haven't been through that yet.

Files up to 1 GB upload straight from your browser. Bigger exports: split by date range, and after the first file's mapping is approved, the rest can go up together.

Step 3 — Review the mapping

The mapping table shows every Unity event type in your file matched to a target event in your tracking plan:

• Unity's automatic events — session and lifecycle tracking — map onto session and player-lifecycle events.
• Transaction events map onto purchase and economy events.
• Your custom events map onto the custom events of your tracking plan; spend your review attention here, since the naming is yours.
• Player identifiers — Unity's user IDs map onto player_id, keeping each player's history in one piece.

Include, exclude, and correct as needed, then submit. A PlayGenus engineer confirms the mapping with you before anything is ingested — and if your export looks different from this page, email us and we'll work through it with you.

What happens after

Your history loads and the dependent models retrain — churn, LTV, survival, and the DAU, revenue, and session forecasts. Dashboards populate as soon as the import lands; predictions follow when retraining completes.

Going forward, your live events come from the PlayGenus SDK — and if your game is built in Unity, that's the Unity client SDK generated from your tracking plan, typed to your events. Old history and new events land in the same dataset: one continuous record, no gap where the migration happened.