Start Building
Business & Monetization Problems Feb 23, 2026

Unity Analytics Not Tracking Events - Data Collection Fix

Unity Analytics not recording or sending events? This guide shows how to fix event tracking, verify the SDK, and get data flowing to your dashboard.

By GamineAI Team

Unity Analytics Not Tracking Events - Data Collection Fix

Problem Statement

Unity Analytics is not recording or sending events: your dashboard stays empty, custom events do not show up, or data appears only after a long delay. This blocks you from measuring player behavior, retention, and monetization and makes it impossible to tune your game with data.

Common symptoms:

  • Analytics dashboard shows no data or zero events
  • Custom events never appear in the dashboard
  • Standard events (e.g. session start, level complete) are missing
  • Data appears only in the Editor, not in the cloud dashboard
  • Events work in Development Build but not in release build

Root Cause Explanation

Unity Analytics can stop tracking events for several reasons:

  • SDK not initialized – The Analytics SDK may not be enabled or started correctly.
  • Project / App ID mismatch – Builds may be using the wrong project or platform app ID.
  • Privacy / consent – User consent or privacy settings can block or delay event sending.
  • Network or platform – Events are batched and sent in the background; connectivity or platform restrictions can block uploads.
  • Event name or parameter errors – Invalid event names or parameters can cause events to be dropped.
  • Build type – Some Analytics features behave differently in Development vs Release builds.

This guide walks you through checks and fixes so events flow reliably to your dashboard.

Quick Fixes (Try These First)

1. Enable and Initialize Unity Analytics

Analytics must be enabled in the project and the SDK must be allowed to run.

Steps:

  1. Open Edit → Project Settings → Services (or Unity Dashboard link).
  2. Ensure the project is linked to a Unity Project ID and that Analytics is On for the project.
  3. In Window → General → Services, open the Services window and confirm Analytics shows as enabled.
  4. In a release build, ensure you are not stripping or disabling the Analytics modules (see Build Settings and Player Settings).

Verification: In the Unity Editor, enter Play Mode and trigger a simple standard event (e.g. level start). Check the Analytics dashboard (with the correct project and app selected) after a short delay; data can take a few minutes to appear.

If this does not work: Continue to the next step.

2. Confirm Project and App ID in Builds

Each platform (e.g. iOS, Android, WebGL) has an App ID. If the build is reporting to the wrong project or app, data will not show in the dashboard you expect.

Steps:

  1. In Edit → Project Settings → Services, note the Project ID and the App IDs per platform.
  2. Build your game and run it on the target platform (or use a Development Build with the same settings).
  3. In the Unity Dashboard, select the same Organization, Project, and App (platform) that match your build. Switch between apps if you have multiple (e.g. iOS vs Android).
  4. Check Analytics → Data (or Events) and apply the correct time range; new events can take 5–15 minutes to show.

Verification: Trigger a known event (e.g. a custom event with a unique name) and look for it in the dashboard under the correct app and time range.

3. Check Consent and Privacy Settings

If you use privacy/consent (e.g. GDPR), Analytics may not send events until the user has consented.

Steps:

  1. If you use Unity Gaming Services or a consent flow, ensure the user has accepted analytics where required.
  2. In code, ensure you are not disabling or delaying Analytics initialization until after consent; otherwise events before consent may be dropped.
  3. In Edit → Project Settings → Privacy, review any settings that might block or delay analytics.

Verification: Run a build where the user has granted consent (or where consent is not required) and confirm events appear.

4. Use Correct Event API and Parameters

Incorrect API usage or invalid parameters can cause events to be ignored.

Steps:

  1. Use the official Analytics API (e.g. UnityEngine.Analytics.Analytics.CustomEvent) with a valid event name (see Unity Analytics documentation).
  2. Keep event names and parameter keys within the allowed character set and length.
  3. Avoid null or invalid parameter values; use simple types (string, number, bool) where possible.
  4. In Development Builds, enable Development Build in Build Settings and check the Editor console or Analytics debug output for errors.

Verification: Call a simple custom event (e.g. Analytics.CustomEvent("test_event");) in Start, run the build, wait a few minutes, and look for that event in the dashboard.

5. Allow Background Sending (Mobile and WebGL)

Events are sent in batches in the background. Some platforms restrict background network or require the app to be in the foreground.

Steps:

  1. On mobile, ensure the app has network permission and is not killing background tasks too aggressively; send a few events, then leave the app open or in foreground for a short time.
  2. For WebGL, ensure the player is allowed to make requests to Unity’s analytics endpoints; ad blockers or strict content security can block them. Test in an incognito window without extensions.
  3. On all platforms, wait at least 5–15 minutes and refresh the dashboard; do not assume real-time reporting.

Verification: Trigger several events, keep the app open for a minute or two, then check the dashboard after a short delay.

Alternative Fixes and Edge Cases

Events only in Editor:
Editor play often uses a different reporting path. Always verify with a built executable (Development or Release) for the target platform.

Development Build vs Release:
Use the same project and app ID in both. Ensure Analytics is not disabled in Release (e.g. via scripting define or build stripping).

Custom Analytics or third-party:
If you use a third-party analytics SDK alongside or instead of Unity Analytics, ensure you are checking the correct dashboard and that the correct SDK is initialized and receiving events.

Prevention Tips

  • Enable Analytics and link the project in Project Settings before building.
  • Use a single, consistent event-naming scheme and document it for your team.
  • Test event flow on a Development Build and on the target platform before release.
  • In code, guard Analytics calls (e.g. try/catch or null checks) so that analytics failures do not affect gameplay.
  • Review Unity Analytics best practices and quotas so events are within limits.

Verification Checklist

  • [ ] Analytics is enabled in Project Settings / Services for the project.
  • [ ] Build is using the correct Project ID and App ID for the platform.
  • [ ] Dashboard is set to the correct Organization, Project, and App (platform).
  • [ ] Consent/privacy is satisfied if required.
  • [ ] Event names and parameters follow the API rules.
  • [ ] You have waited 5–15 minutes and refreshed the dashboard.
  • [ ] You tested with a built executable, not only in the Editor.

Related Problems and Links

  • Unity Analytics Dashboard empty: Often the same root cause; use the steps above and confirm project/app and delay.
  • Unity Build Fails or scripting errors: Fix build and scripting errors first so Analytics code can run.
  • Ad integration or monetization issues: See Ad integration not working for separate but related setup.

For more on game analytics and business metrics, see our guides and courses. Bookmark this fix for quick reference; if it helped, share it with your dev team.