Summary

• No cookies are used for player analytics.
• No PII is stored in the metrics store. Events carry only IDs (e.g., datapointId, playerId) and player metadata.
• Session is derived server-side from the user’s IP using a one-way hash and saved as sessionId.
• Events are sent from the player in the browser to SEEN’s metrics collection service and stored in SEEN’s analytics datastore.
• Linking events to an identifiable receiver only happens at export (or via authorized API) inside your workspace.

What gets tracked (events)

The SEEN web player emits a small set of product events:

• player-opened
• video-played
• video-playing (heartbeat/position)
• video-watched (completion)
• cta-clicked
• share-clicked

These are first-party events used to measure player delivery, engagement and CTA performance for a given personalised video.

<aside>

Related article: Dashboard documentation

</aside>

Payload structure