Player Events

1. Two ways to receive them

For a specific screen you can listen CustomEvent about the Player. For a centralized integration use emitEvent; This way you don't depend on mounting different listeners in each view.

const player = document.querySelector('p2lrn-player');

player.addEventListener('p2lrn:score', (event) => {
  console.log(event.detail);
  console.log(event.detail.event);
});

In DOM, payload fields appear directly in event.detail, along with event.detail.context and the complete canonical envelope in event.detail.event.

2. Canonical envelope

The object you receive HostAdapter.emitEvent(event, context) It always maintains the same envelope, regardless of the renderer that originates it.

{
  "schema": "https://p2lrn.org/schema/runtime-event/1",
  "version": "1",
  "type": "p2lrn:complete",
  "timestamp": "2026-10-16T08:30:00.000Z",
  "context": {
    "packageId": "urn:uuid:...",
    "contentRoot": "sha256:...",
    "entityId": "urn:uuid:...",
    "resourceId": "urn:uuid:...",
    "representationId": "urn:uuid:...",
    "rendererId": "https://p2lrn.org/renderer/..."
  },
  "payload": {}
}

schema and version identify the contract; type identifies the event; timestamp it is runtime time; context locate the content; payload contains the specific data.

3. Loading and rendering events

4. Interaction events

5. Status, score and completion

6. H5P and xAPI

H5P can issue xAPI statements. P2LRN exposes them without converting them into the platform's trusted identity.

If you are sending xAPI to an LRS, rebuild actor, authority, registration/intent, and other trust fields on your platform server.

7. Errors

p2lrn:error includes a phase when the implementation knows the phase that failed. It can appear when loading the package, rendering content, saving state, reporting note, sending events, resolving sequencing, or executing a runtime.

The technical error is used for diagnosis. Your application interface should decide what message is taught to the learner and what errors are recoverable.

8. Order and persistence with Host Adapter

The calls to emitEvent are serialized by Adapter: one event is delivered after the previous one. If your callback fails, P2LRN locally produces a p2lrn:error phase emitEvent without recursively forwarding that same error to the Adapter that is failing.

For an analytical history, keep the canonical envelope. To resume use saveState; do not try to reconstruct the current state by reproducing the entire event log unless your platform has expressly designed it that way.

9. What events to save

It is not mandatory to store all events. A platform can save only notes/status, or maintain a full log if you need detailed analytics.

10. Names you should use

The guide Metrics and analytics explains what to extract from quizzes, SCORM, H5P and progression and how to associate it with learner and attempt.

Intents and rich interactions

Native quizzes now emit explicit intent and interaction cycle events so that a platform can distinguish start, resume, and deliver without rebuilding them from the DOM.