3. Telemetry Collection
Controlling high-resolution behavioral tracking.
Starting and Stopping Capture
While the NX10 SDK requires zero manual instrumentation of your UI or input systems, telemetry collection does not start automatically when you initialize a session.
This is by design. It gives you granular control over when NX10 receives kinematic sensor data. Calling StopTelemetry() stops the SDK from collecting Telemetry data (touch, accelerometer, and gyroscope), while allowing the active session to continue collecting Events and Attributes (via SendEvent, SendOutcomeEvent, and SetAttribute). Calling StartTelemetry() resumes kinematic telemetry capture.
While we strongly recommend capturing telemetry throughout the entire consented app experience (menus are often a massive source of undetected frustration), you may wish to temporarily pause telemetry during sensitive password inputs or specific cutscenes without interrupting event or attribute tracking.
Consent Withdrawal: Use StopSession(), Not StopTelemetry()
StopTelemetry() only pauses kinematic sensor data—Events and Attributes continue to be collected while the session remains open.
Do not call StartSession() until the user has granted consent, and if a user withdraws consent, you must call NX10Manager.Instance.StopSession() to stop all data collection completely. See 1. Initialization & Consent for the full consent lifecycle.
Zero Instrumentation
Once you call StartTelemetry(), the SDK automatically hooks into Unity's native input systems. You do not need to wrap your buttons, rewrite your raycasters, or manually push events. It all happens silently in the background.
The API Surface
Simply call these methods anywhere in your game loop after the session has successfully started.
using NX10;
using UnityEngine;
public class GameplayManager : MonoBehaviour
{
public void OnEnterMainGameLoop()
{
// Begin capturing touches, gyro, and accelerometer
NX10Manager.Instance.StartTelemetry();
Debug.Log("NX10 Telemetry Active");
}
public void OnEnterSecurePasswordScreen()
{
// Pause kinematic telemetry capture instantly;
// Events and Attributes continue to work normally while the session remains active
NX10Manager.Instance.StopTelemetry();
NX10Manager.Instance.SetAttribute("view", "password_entry");
Debug.Log("NX10 Telemetry Paused (Events & Attributes still active)");
}
}What does the SDK capture?
When telemetry is active, the SDK seamlessly collects:
- General Touch Events: Down, Move, Up events with highly accurate X/Y coordinates, pressure, and velocity.
- Keyboard Touch Events: Specific touches associated with on-screen keyboard interactions (if applicable).
- Gyroscope Readings: Rotational velocity of the device.
- Accelerometer Readings: Linear acceleration of the device.
Network & Performance Optimization
High-resolution telemetry generates a massive amount of data. Sending standard JSON objects for every touch frame would instantly overload mobile networks and battery life.
The NX10 SDK solves this by encoding events into highly compressed, fixed-order Tuples. Furthermore, rather than stamping every event with a heavy ISO-8601 string, the SDK generates a single base UTC timestamp for a "capture window" and records all events simply as millisecond offsets from that base time. This allows NX10 to receive granular 120hz data with a virtually undetectable network footprint.
