Unity 6 is a milestone release centered on one critical goal: making the Unity Engine faster, more stable, and more reliable across every platform and deployment environment. But achieving that level of performance at scale requires more than internal testing or synthetic benchmarks. It requires real, timely insight into how the engine behaves in production—on actual devices, in real-world gameplay, across the full spectrum of player environments.

That’s where diagnostic data—and more broadly, Developer Data—becomes essential. Diagnostic data is just one type of Developer Data that’s collected by the Unity Engine at runtime to help improve performance, compatibility, and reliability. It includes crash logs, Application Not Responding (ANR) errors, error traces, and other core telemetry. Enabled by default in new projects, starting with Unity 6.2, it allows Unity to detect and resolve issues quickly—often before you or your players even notice them.

Starting in Unity 6.2, new projects created in the Unity Hub are configured to collect diagnostic data by default in the Unity Editor. This data is considered essential for your use of the Unity engine and is collected automatically so long as the project is linked to the Unity Dashboard. Diagnostic data collection being enabled is also what allows for the collection of Developer Data from your apps in general–in accordance with your Developer Data collection settings. If you choose to disable diagnostic data collection, Unity halts all Developer Data collection entirely, including for services that rely on it.

But that’s only the starting point. When you choose to fully configure your Developer Data through the Unity Dashboard, you gain fine-grained, real-time control over how Developer Data is collected and used. You can toggle on Additional Recommended Data—a curated set of signals Unity offers to collect for your benefit, derived from the engine’s unique runtime observability. This Recommended Data isn’t strictly required for service functionality, but it adds a layer of context to your Developer Data that is designed to make it more useful overall.

In addition to data collected from the runtime, you can also link external sources—like Google Analytics—and manage them along with your other Developer Data. Whether it originates from Unity’s engine or your analytics stack, all Developer Data is governed through the same consistent, transparent interface.

The same infrastructure that helps Unity improve the engine is the foundation of Developer Data. As you incorporate more of your own data—gameplay telemetry, behavioral insights, purchase signals—you unlock more of Unity’s capabilities. From performance to personalization, from diagnostics to support, the Developer Data framework makes your data work harder for you.

And in Unity 6 and beyond, your data improves your experience—this framework makes it transparent, intentional, and easy.