ActivityCompletedEvent
Emitted once per activity run when the student completes the activity. Carries completion metrics like questions answered, XP earned, and mastery.Activity metrics
Thegenerated.items array contains completion metrics. Each item has a type (string) and a value (number).
number
required
XP supplied by your app for this activity. Follow the XP policy agreed for your integration.
The SDK does not infer XP from elapsed time or question counts.
number
Total questions in the activity. Optional, but required if
correctQuestions is provided.number
Questions answered correctly. Optional, but required if
totalQuestions is provided.number
Number of new units (lessons) the student mastered during this activity. This is an
incremental count, not a cumulative total. When this value is positive, the SDK server can
combine it with historical enrollment facts and a configured positive
totalLessons to
compute pctCompleteApp, unless you supplied pctComplete explicitly. If enrollment or
historical facts cannot be resolved, computation can be skipped. Optional. See Course
progress for full details.number
Course completion percentage (0—100). Either passed directly via
pctComplete in the activity
payload, or auto-computed by the server from masteredUnits and
totalLessons. Sent
via generated.extensions.pctCompleteApp. See Course
progress.TimeSpentEvent
The SDK sends periodic heartbeats every 15 seconds by default and flushes measured time when an activity ends. The server uses that measured time to construct TimeSpentEvents. Each event reports a bounded time window; a heartbeat is not itself proof that a Caliper event or analytics fact was persisted.Time metrics
Thegenerated.items array contains time window metrics. Each item has a type (string), a value in seconds (max 86400), and optional fields.
Time categories
number
Seconds the student was actively engaged (tab visible, not paused).
number
Seconds the student was inactive (paused or tab hidden).
number
Seconds classified as non-productive.
number
Seconds that could not be classified.
number
Seconds flagged as anomalous behavior.
Per-item fields
string
Optional sub-classification providing additional detail on the time category.
string
ISO 8601 timestamp for the start of the time window.
string
ISO 8601 timestamp for the end of the time window.
Acceptance and delivery
An accepted Caliper request does not confirm XP, reporting, or progression completion. Preserve each event ID and the original payload across transport retries. A new event ID can represent new work to a downstream consumer. An activity’sCompleted action does not by itself assert that the whole course is complete.
Shared structure
Both event types share these top-level fields:string
required
Caliper JSON-LD context. Always
"http://purl.imsglobal.org/ctx/caliper/v1p2".string
required
Unique event identifier in
urn:uuid:... format.string
required
"ActivityEvent" for completions, "TimeSpentEvent" for time windows.string
required
"Completed" for completions, "SpentTime" for time windows.string
required
Always
"TimebackProfile".string
required
ISO 8601 timestamp of when the event occurred.
TimebackActivityContext
required
The activity context where the event was recorded.
object
required
Metrics collection. Shape depends on event type:
- ActivityCompletedEvent
- TimeSpentEvent
Type:
TimebackActivityMetricsCollectionstring
Application context on the event. Its accepted representation depends on the target contract.
object
Custom attributes including
runId and courseId for event correlation.string
Entity representing a particular segment or location within the object.
string
Entity representing the referring context.
string | object
An Organization representing the group context. Can be a URL or an Organization entity object.
string
The relationship between the actor and the group in terms of roles and status.
string
The current user session.
string
If the event occurs within an LTI platform launch, the tool’s LtiSession.
Custom Activities
How the SDK emits these events
Caliper API
Direct Caliper API access for custom event submission