Skip to main content

Session identity and lifecycle

When sessionId is a valid UUID, Ramon uses it directly. Otherwise, the embed generates a UUIDv7 and stores it in sessionStorage under a key scoped to the tracking key. It reuses that identifier only while the interviewId remains the same.

This provides sensible default session continuity for a browser tab, but an integration that must map a score or deletion to a platform response should generate and supply its own UUID.

  1. Generate a UUID when your platform creates a response.
  2. Render it as sessionId and interviewId in window.ramonConfig.
  3. Store the UUID with your response, not in a survey answer field.
  4. Send that UUID to the Integration API for lookups and deletion requests.

Do not use a participant email address, token, or answer value as a Ramon session reference.