The Inkrypt native SDKs track playback analytics automatically. This guide explains how that surfaces in a React Native integration, which is to say, transparently, and where the platforms differ.
TL;DR
- You do not need to configure or call anything from React Native. Analytics are owned by the native SDKs and begin the moment a video loads.
- What is tracked, how it is transported, and where it goes depends on the platform. The iOS SDK pushes to Inkrypt's analytics endpoint automatically. The Android SDK can push to a configurable endpoint you set in the Inkrypt Dashboard.
- All tracked data is aggregated in the Inkrypt Dashboard.
How the React Native Layer Is Involved
It isn't, and that's intentional. The wrapper does not sit in the analytics path. Every analytics event originates from, and is dispatched by, the native player running inside the view. The React Native layer's only responsibility is to pass videoId and otp into the native component, which both SDKs then use to associate events with a session.
There is currently no React Native API to observe analytics events from JS.
Platform Behavior
The two native SDKs implement analytics quite differently. The summary below covers the headline differences, the linked native docs are the authoritative reference.
iOS: Always-On, Server-Owned Destination
The iOS SDK tracks 11 event types across the video lifecycle and ships each event to Inkrypt's analytics backend automatically:
setup · startup · playing · play · pause · seeking · bufferingStart · bufferingEnd · qualityChange · ended · close
Per-event payloads include session and device metadata (session ID, persistent user ID, video timing, bitrate, resolution, device type). Analytics cannot be disabled via the public API today — reach out to Inkrypt for compliance use cases.
For the full event list, payload schema, and privacy notes, see: native iOS — Live Analytics Guide.
Android: Dashboard-Configured "App Push Live Analytics"
The Android SDK supports a per-video feature called App Push Live Analytics. When enabled on a video in the Inkrypt Dashboard, the SDK periodically POSTs a small payload to a URL you configure:
userId- derived from the video's watermark label (Base64)videoId·otptotalPlayedTimeInSeconds·currentPositionInSeconds
The interval and destination URL are both set in the dashboard, not in app code. The SDK pauses pushes when the app is backgrounded and stops them if the server returns >= 400.
For the full payload schema, HTTP response handling, and lifecycle details, see: native Android — Live Analytics Guide.
Privacy
Neither SDK transmits audio or video content. Tracked data is behavioral, timing, bitrate, resolution, device class, plus a randomly generated (or watermark-derived) user ID.
If your app handles regulated data (GDPR, CCPA, App Store privacy labels), the native docs include the full list of fields collected so you can disclose accurately: