NEW: Insights analytics support for the Input System by K-Tone · Pull Request #2272 · Unity-Technologies/InputSystem

K-Tone · 2025-10-30T14:58:28Z

Description

This PR brings support for the Insights analytics module to Input System.

Requires native side PR to land first: https://github.cds.internal.unity3d.com/unity/unity/pull/83832

Currently, we send these kinds of data to Insights:

When a new input device is connected, we send this information:

product (" DUALSHOCK 4 Wireless Controller")
serial ("A0:5A:5E:92:0F:3E")
version ("1.0")
interface ("HID")

When an input device is disconnected, we send this information:

serial (really intended to be matched with the event above at the time of analysis)

When a new Input Action Map is being loaded or activated, we scan for all the Input Actions that are being brought to life and for each one, we send the following data:

name (e.g. "Jump")
type (e.g. "Button")

Testing status & QA

Local testing

Overall Product Risks

Complexity: Low
Halo Effect: Low

Checklist

Before review:

Changelog entry added.
- Explains the change in Changed, Fixed, Added sections.
- For API change contains an example snippet and/or migration example.
- JIRA ticket linked, example (case %%). If it is a private issue, just add the case ID without a link.
- Jira port for the next release set as "Resolved".
Tests added/changed, if applicable.
- Functional tests Area_CanDoX, Area_CanDoX_EvenIfYIsTheCase, Area_WhenIDoX_AndYHappens_ThisIsTheResult.
- Performance tests.
- Integration tests.
Docs for new/changed API's.
- Xmldoc cross references are set correctly.
- Added explanation how the API works.
- Usage code examples added.
- The manual is updated, if needed.

During merge:

Commit message for squash-merge is prefixed with one of the list:
- NEW: ___.
- FIX: ___.
- DOCS: ___.
- CHANGE: ___.
- RELEASE: 1.1.0-preview.3.

After merge:

Create forward/backward port if needed. If you are blocked from creating a forward port now please add a task to ISX-1444.

ekcoh

Looks good, but would suggest to use interface similar to other module facing calls given the current test fixture design.

Packages/com.unity.inputsystem/InputSystem/Actions/InputActionState.cs

K-Tone · 2026-01-20T16:07:12Z

Packages/com.unity.inputsystem/InputSystem/Unity.InputSystem.asmdef

+        },
+        {
+            "name": "Unity",
+            "expression": "6000.5.0a5",


This will have to be changed to whatever is the actual Unity version we happen to release Input insights in. We will know that once the native PR lands. Then we will change this for every backport

ekcoh · 2026-01-21T14:07:14Z

Packages/com.unity.inputsystem/Tests/TestFixture/InputTestRuntime.cs


-        #endif // UNITY_ANALYTICS || UNITY_EDITOR
+        // We don't want to populate Insights from within tests, even when running them in players
+        public void LogDeviceConnectedInsight(InputDeviceDescription description)


Might want to store these in harness in case you want to test it in the package

ekcoh · 2026-01-21T14:09:33Z

Looks like you need to (re)run formatter on this one

rohit-moni · 2026-01-22T18:58:59Z

Packages/com.unity.inputsystem/InputSystem/InputManager.cs

+            m_Runtime.LogDeviceConnectedInsight(description);
+


I see that logging the input action is bracketed by the new define UNITY_INPUT_SYSTEM_SUPPORTS_INSIGHTS. Should this also be conditional on it?

rohit-moni · 2026-01-22T18:59:16Z

Packages/com.unity.inputsystem/InputSystem/InputManager.cs

+                            m_Runtime.LogDeviceDisconnectedInsight(device.description);
+


Similar: should this be #if UNITY_INPUT_SYSTEM_SUPPORTS_INSIGHTS?

rohit-moni · 2026-01-22T19:02:14Z

Packages/com.unity.inputsystem/InputSystem/NativeInputRuntime.cs

+        public void LogInputActionInsight(InputAction action)
+        {
+#if UNITY_INPUT_SYSTEM_SUPPORTS_INSIGHTS && !UNITY_EDITOR
+            NativeInputSystem.LogInputActionInsight(action.name, action.type.ToString());


Not too familiar with input actions, I'm worried that enabling this will add a string allocation to every input action, resulting in two potential issues: performance degradation of all inputs (allocation perf) and frequent / large garbage collection (after many disparate allocations). Can this be cached? Do we have the action type string already stored somewhere? Is there another reason that invalidates the concern?

rohit-moni · 2026-02-04T14:20:53Z

Packages/com.unity.inputsystem/InputSystem/Actions/InputActionState.cs

+#if UNITY_INPUT_SYSTEM_SUPPORTS_INSIGHTS
+            // also report all actions to insights
+            foreach (var inputAction in map.actions)
+            {
+                InputSystem.s_Manager.m_Runtime.LogInputActionInsight( inputAction );
+            }
+#endif


Was looking at this again and am a little confused. Is LogInputActionInsight for when the InputAction happens, or for when it's enabled?

I think as it is right now, we're sending insights for all the actions, but only once (when they're all enabled). We're not tracking when the actions happen. Is that the intent?

an example use case for the new vector analytics api

c93bcdb

K-Tone force-pushed the anthony/vector-analytics branch from 70a4618 to c93bcdb Compare January 16, 2026 10:26

K-Tone added 4 commits January 20, 2026 10:46

extend device connection insight with more information

d0b8bb6

add device disonnected event

5c50794

guard insights with version-dependent define

31832b7

punch input actions stored in the action maps through to insights

1dbbc48

K-Tone changed the title ~~an example use case for the new vector analytics api~~ Implement Insights analytics for device connect and disconnect events, and also for all Input Actions that are spawned from Input Action Maps Jan 20, 2026

K-Tone changed the title ~~Implement Insights analytics for device connect and disconnect events, and also for all Input Actions that are spawned from Input Action Maps~~ Insights analytics support for the Input System Jan 20, 2026

ekcoh reviewed Jan 20, 2026

View reviewed changes

Packages/com.unity.inputsystem/InputSystem/Actions/InputActionState.cs Outdated Show resolved Hide resolved

K-Tone commented Jan 20, 2026

View reviewed changes

K-Tone added 4 commits January 21, 2026 13:14

use insights via an interface as suggested during reviews

e7794d2

use insights via a proxy interface

32d53c5

removed unused includes

d36d8fd

don't send any data from within editor

f42157a

ekcoh approved these changes Jan 21, 2026

View reviewed changes

ekcoh changed the title ~~Insights analytics support for the Input System~~ NEW: Insights analytics support for the Input System Jan 21, 2026

rohit-moni reviewed Jan 22, 2026

View reviewed changes

rohit-moni reviewed Feb 4, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

NEW: Insights analytics support for the Input System#2272

NEW: Insights analytics support for the Input System#2272
K-Tone wants to merge 9 commits intodevelopfrom
anthony/vector-analytics

K-Tone commented Oct 30, 2025 •

edited

Loading

Uh oh!

ekcoh left a comment

Uh oh!

Uh oh!

K-Tone Jan 20, 2026

Uh oh!

ekcoh Jan 21, 2026

Uh oh!

ekcoh commented Jan 21, 2026

Uh oh!

rohit-moni Jan 22, 2026

Uh oh!

rohit-moni Jan 22, 2026

Uh oh!

rohit-moni Jan 22, 2026 •

edited

Loading

Uh oh!

rohit-moni Feb 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

K-Tone commented Oct 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Testing status & QA

Overall Product Risks

Checklist

Uh oh!

ekcoh left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

K-Tone Jan 20, 2026

Choose a reason for hiding this comment

Uh oh!

ekcoh Jan 21, 2026

Choose a reason for hiding this comment

Uh oh!

ekcoh commented Jan 21, 2026

Uh oh!

rohit-moni Jan 22, 2026

Choose a reason for hiding this comment

Uh oh!

rohit-moni Jan 22, 2026

Choose a reason for hiding this comment

Uh oh!

rohit-moni Jan 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rohit-moni Feb 4, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

K-Tone commented Oct 30, 2025 •

edited

Loading

rohit-moni Jan 22, 2026 •

edited

Loading