Skip to main content

Behaviors Tracking Data

Data collected for each behavior assigned to students in LiftEd BI Export

Updated today

The Behaviors Tracking Data dataset provides detailed information about each recorded behavior data entry assigned to students within the district in LiftEd.


This page explains the structure and contents of the behavior_tracking_<date>_<time>.csv file included in your LiftEd BI Data Export.

Each record in this dataset represents a single behavior data entry and includes the identifiers needed to connect with Students, Staff, and Behaviors.

The column order listed here will be left to right in the export

Filename: behavior_tracking_<date>_<time>.csv

Column

Data Type

Example Value

Data Definitions

behavior_id

GUID

Eg: 6f4ec37f-1023-4df5-8aaa-1234567890ab

Which behavior was observed

staff_id

GUID

Eg: 1574abb5c-0aa0-5117-b305-1234567890ab

Who recorded the observation (staff)

student_id

GUID

Eg: abc2a3d0-4cde-453e-bc02-1234567890ab

Which student this entry is about

date

DateTime

Eg: 2025-02-20T11:03:52.811+00:00

When the observation started

observation_period

int

Eg: 300

Length of the observation window (seconds)

intervals_with_behavior

int

Eg: 6

Number of intervals where behavior occurred. Only Checkmark in ui, not x mark

total_intervals

int

Eg: 125

Total intervals observed

percentage

float

Eg: 0.5

percentage of intervals_with_behavior / total_intervals

has_percentage_override

boolean

Eg: FALSE

manual percentage input by user

duration

int

Eg: 451

Total seconds behavior occurred in the window

frequency

int

Eg: 36

How many times the behavior happened

location

Array<LocationEnum> | string

Eg: Playground; Classroom

Where the observation took place

notes

string

Eg: Observed minor distractions.

Free-text notes from the observer

is_deleted

Boolean

Eg: True or False

Indicates if the record has been soft delet

Example: behavior_tracking_20251028_161014.csv

Tip: Click on the image to view it in full size, and click < to go back.


​

Did this answer your question?