Listen to events

The Moviie Player emits a stable set of events that mirror the underlying playback lifecycle. Use them to drive analytics, sync your UI with the viewer's actions, or trigger downstream behaviour.

Subscribing

Use on(event, handler) to subscribe and off(event, handler) to unsubscribe. on returns an unsubscribe function for convenience.

const unsubscribe = window.Moviie.on('play', () => {
  console.log('playback started')
})

// later
unsubscribe()

For one-shot subscriptions (e.g. waiting for the first ready event), prefer once:

window.Moviie.once('ready', () => {
  console.log('player ready')
})

Reading payloads

Some events carry a payload: see the table below for the exact shape.

window.Moviie.on('timeupdate', ({ currentTime }) => {
  progressBar.value = currentTime
})

Events without a documented payload fire with no arguments.

unmute is emitted once when the viewer first activates audible playback in an autoplay-muted session. Muting and unmuting again does not create another funnel engagement event for the same telemetry session. It is an observable player event; it does not expose viewer identity or conversion data.

Event reference

Tips

• Throttle high-frequency handlers: timeupdate fires every ~250ms. Coalesce expensive work (analytics flushes, layout reads) before reacting.
• Always unsubscribe: long-lived listeners outlive the player when you destroy and recreate the embed (e.g. between routes). Call unsubscribe() or off(event, handler) in your cleanup path.
• Combine with getState(): events tell you when something happens; getState() tells you what the player looks like at that moment. See getState.