Sealed Client Results
New encrypted payload delivery eliminates the need for separate Server API calls to get full event data.
April 11, 2026 · Feature
Sealed Client Results
Sealed client results deliver full event data directly in your browser's identify() response, encrypted with AES-256-GCM so only your backend can decrypt it. This eliminates the latency of making separate Server API calls while keeping sensitive signal data secure.
Benefits
- Faster integration: Get complete event data synchronously without additional API requests
- Reduced latency: No round-trip delays for server-side event retrieval
- Enhanced security: Browser never sees raw signal data, only encrypted payloads
The encrypted payload contains the same comprehensive event data available through the Server API, including all signals and metadata your backend needs for decision-making.
Back to Changelog.