Classes & Analytics
TeachFORGE.ai
Classes & Analytics / Exporting
Exporting analytics
Getting the figures out, with no export settings to get wrong.
Filter first. The export is the view.
One rule
Every export mirrors the view it came from. The surfaces, the date range, the class and every per-surface filter apply to the file exactly as they apply to the screen.
So there is nothing to configure. Narrow the view until it shows what you want, then press Export CSV. The button reports Exporting… while it works and says plainly when it fails.
This also means an export inherits the truncation notice. If the screen warned that not everything in the range was counted, the file has the same gap and does not say so. Export a shorter range or one class when the figures need to be exact.
Where the exports are
| Export | From |
|---|---|
| Class report | The class report header |
| Activity | The Activity tab |
| Delivery results | A delivery's own results panel |
| Learning record entries | A learner's record from the class roster |
| Attempts | The same page, as a second export |
The delivery export is the one that usually feeds a mark book, and the class report export the one that feeds a progress conversation.
What is in them, and what is not
Handles and aliases, never names — including from a class linked to a learning platform, where names are fetched for display and never exported.
Anonymous link plays are in the totals and not in the rows, because they belong to nobody. A file whose rows sum to less than the tile above it is usually that, rather than a fault.
Handling the files
An export is a list of handles and what each did, which is not identifying on its own — and becomes identifying the moment it sits beside your handle-to-name list.
Treat a downloaded export the way you would treat a mark book: on a device you control, shared deliberately, and deleted when it has done its job. The platform's care with learner identity ends at the point the file leaves it.