Start Building

Problem Summary

You have Unity Analytics (or Unity Gaming Services Analytics) set up in your project, but the dashboard shows no data, empty charts, or "No data available" even after running the game and triggering events. This is common when the project is not linked correctly, events are not being sent, or the dashboard is looking at the wrong property or date range.

This guide walks you through the most likely causes and fixes so your analytics data starts showing up.

Step 1 – Confirm Project and Dashboard Are Linked

Unity Analytics data appears in the Unity Dashboard (dashboard.unity.com) or the Unity Gaming Services console, not inside the Unity Editor. The project in the dashboard must match the Organization and Project that your game is sending data to.

  1. In Unity, open Edit → Project Settings → Services (or Unity Gaming Services in newer versions).
  2. Note the Project ID and Organization shown. You must be logged in with the same Unity account that owns that project.
  3. In a browser, go to dashboard.unity.com or the UGS console and open the same project (same name and ID).
  4. In the dashboard, open Analytics (or Analytics & Data). Ensure you are viewing the correct project, not a different one or a default project.

If the project was recently created or re-linked, the dashboard can take a few minutes to show the correct project. If you have multiple projects, it is easy to have the wrong one selected.

Verification: In the dashboard, check the project name and ID in the header or settings. They must match Project Settings → Services in Unity.

Step 2 – Ensure Events Are Being Sent (Runtime)

The dashboard only shows data when your built game (or Play Mode build) actually sends events to Unity’s servers. If no events are sent, the dashboard will stay empty.

  1. Enable Analytics in Unity: In Project Settings → Services, ensure the Analytics (or Gaming Services Analytics) service is On and linked to the correct project.
  2. Use the Analytics API or built-in events: Your game must call the Analytics API (e.g. Analytics.CustomEvent, AnalyticsEvent.ScreenVisit) or use components that send standard events. If you never call these, no custom or standard events are sent.
  3. Run a real build: Data is often sent only from development or release builds, not always from the Editor. Build your game (e.g. Windows/Mac standalone or a mobile build), run it, play for a minute, trigger a few actions (e.g. level start, button click), then close the game. Wait 15–60 minutes and check the dashboard again.
  4. Check for errors: In the Unity Editor console, look for Analytics-related errors (e.g. "Analytics not initialized", "Invalid project ID"). Fix any initialization or configuration errors so events can be sent.

Pro tip: Send a simple custom event (e.g. "test_event") from a script when the game starts, then run a build and confirm that event appears in the dashboard after a short delay. That confirms the pipeline is working.

Step 3 – Wait for Processing and Check Date Range

Unity’s servers do not show data instantly. There is usually a delay (often 15 minutes to a few hours) before events show up in the dashboard.

  1. Wait at least 15–30 minutes after running the game and sending events before concluding that data is missing.
  2. In the dashboard, set the date range to Today or Last 7 days. If the range is set to a future date or a very old range, you will see no data.
  3. Refresh the page or switch to another report and back. Sometimes the dashboard caches an empty state.

Verification: Send a test event, wait 30–60 minutes, set the date range to "Today", and refresh. If data still does not appear, continue to the next steps.

Step 4 – Check Privacy and Consent (GDPR / Data Collection)

In some regions or with certain settings, data collection can be disabled until the user consents (e.g. GDPR). If consent is required and not given, events may not be sent or may be dropped.

  1. In Project Settings → Services → Analytics (or the Analytics section in UGS), check for Privacy or Consent options.
  2. If you have "Require user consent" or similar enabled, ensure your game requests and records consent and that the Analytics SDK is told that consent was given (via the appropriate API). Otherwise events may not be sent.
  3. For testing, you can temporarily disable consent requirements so that all events are sent; re-enable before release if your policy requires consent.

Step 5 – Verify Network and Build Settings

Events are sent over the network. If the build cannot reach Unity’s servers, no data will appear.

  1. Run the build on a machine with internet access. Firewalls or corporate networks can block analytics endpoints; test from a different network if possible.
  2. Check build settings: Some stripped or minimal builds might exclude the Analytics SDK. Ensure the Analytics package or module is included in the build (e.g. not stripped by link.xml or build options).
  3. Platform-specific: On mobile, ensure the app has network permission and is not blocking outbound HTTPS. On WebGL, check CORS and that the build is allowed to call Unity’s analytics domain.

Alternative Fixes and Edge Cases

  • Multiple projects: If you copied the project or have two projects with similar names, confirm you are not sending to one project and viewing another in the dashboard.
  • New project: Brand-new Unity Gaming Services projects can take longer for the first data to appear. Wait up to 24 hours for the first events, then re-check.
  • Deprecated Analytics: If you are on the legacy Unity Analytics (pre–Gaming Services), migration to the new system may be required; check Unity’s current documentation for your Unity version.

Prevention Tips

  • Link Services once at project creation and avoid changing Organization/Project ID after you start sending data.
  • Send at least one test event in every build type (development, release) to confirm the pipeline.
  • Document your project ID in your team wiki so everyone checks the correct dashboard project.

Verification Checklist

  • [ ] Project in dashboard matches Project Settings → Services (same project ID).
  • [ ] Analytics service is On in Project Settings.
  • [ ] Game sends events (custom or standard) from a real build.
  • [ ] Waited at least 15–30 minutes and set dashboard date range to Today.
  • [ ] No Analytics errors in the Unity console or build logs.
  • [ ] Privacy/consent settings allow sending events (for your test environment).

When the project is linked correctly, events are sent from a build, and the date range is correct, the dashboard should start showing data. If it still does not, check Unity’s Analytics documentation for your Unity version and the current event format and dashboard location.

Bookmark this fix for quick reference. If you are also setting up monetization or ads, see our Ad Integration Not Working and Unity Analytics Not Tracking Events articles for related steps.