Skip to main content
The Timeback SDK emits Caliper-based events to report learning activity.
See Activity Models for when each event is emitted.

ActivityCompletedEvent

Emitted once per activity run when the student completes the activity. Carries completion metrics like questions answered, XP earned, and mastery.

Activity metrics

The generated.items array contains completion metrics. Each item has a type (string) and a value (number).
number
required
XP earned for this activity. Must follow the 1 XP = 1 focused minute rule.
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. The server sums these values across submissions and uses them to auto-compute pctCompleteApp. 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

Emitted periodically during a session (every 15s by default) and on final flush. Each event covers a bounded time window — how many seconds were active vs inactive.

Time metrics

The generated.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.

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.
TimebackUser
required
The student who performed the action. See Identity.
TimebackActivityContext
required
The activity context where the event was recorded.
object
required
Metrics collection. Shape depends on event type:
Type: TimebackActivityMetricsCollection
string
URL identifying the application context (standard Caliper envelope field).
object
Custom attributes including runId and courseId for event correlation.
Both events also accept these optional Caliper envelope fields:
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