Report types reference
The original draft described parameters/output columns for 3 separate report types (Customer Traffic, Customer Presence, Check Meeting). On the live Portal, this is a single unified form parameterized by Event Type — see Generating and exporting reports for the real form structure. Confirmed directly (2026-07-21) that the Event Type dropdown has exactly 5 values, matching the task-creation Detection Event list: Đếm người (People Counting), People Tracking, Restricted Area Alert, Đếm người body (People Counting – body detection variant), Check họp đầu ca (Shift Meeting Check) — not the 3 "Customer Traffic/Customer Presence/Check Meeting" values assumed in the original draft. A full Generate run wasn't completed (blocked by the required Location field not being selectable correctly during testing), so the actual output columns and CSV format remain unconfirmed — the table below keeps the original draft's content as a hypothesis, mapped to the closest matching Event Type.
Reference for input parameters and data fields, mapped as a hypothesis from each original "report type" to an Event Type value in the unified Report form — see Generating and exporting reports for the workflow.
Confirmed Event Type values
| Event Type | Hypothesized mapping to original "report type" |
|---|---|
| Đếm người (People Counting) | Customer Traffic / Customer Presence (hypothesis) |
| People Tracking | (no mapping in the original draft) |
| Restricted Area Alert | (no mapping in the original draft — see Restricted zone check) |
| Đếm người body (People Counting – body detection variant) | (no mapping in the original draft) |
| Check họp đầu ca (Shift Meeting Check) | Check Meeting (hypothesis) |
Common input parameters (Report form)
Apply to every Event Type — see Generating and exporting reports for details:
| Parameter | Required | Description |
|---|---|---|
| Event Type | Yes | The event/report type |
| Customer Type | Yes | All / Customer / Others |
| Data Type | Yes | Raw / Aggregate |
| Region / Area / Brand | No | Hierarchical location filters |
| Location | Yes | A specific location |
| Date range | Yes | Today / Last 7 days / Last 30 days / custom From-To |
Customer Traffic — hypothesis, needs verification
Detail table (Data Type = Aggregate)
| Field | Description |
|---|---|
| Region, Area, Brand, Cost center code, Location | Location metadata |
| Date | DD/MM/YYYY |
| Shift | Work shift (Shift 1, Shift 2, ...) |
| Total customers | Total unique customers |
Customer Presence — hypothesis, needs verification
Data table (Data Type = Raw)
| Field | Description |
|---|---|
| Location, Cost center code, Brand | Location metadata |
| Date | DD/MM/YYYY |
| Shift | Work shift |
| Recognition ID | Customer recognition ID |
| First / last appearance | HH:MM AM/PM |
| Duration | HH:MM:SS |
Check Meeting — hypothesis, needs verification
Corresponds to Event Type = Check họp đầu ca (Shift Meeting Check) — see Configuring Task AI.
Compliance status
| Status | Description |
|---|---|
| On time | Held on time (within the allowed window from shift start) |
| Late | Held, but after the allowed window |
| Not held | No meeting detected during the shift |
Detail table
| Field | Description |
|---|---|
| Region, Area, Brand, Cost center code, Location | Location metadata |
| Date, Shift | — |
| Meeting time | Blank if not held |
| Meeting duration | Blank if not held |
| Number of attendees | — |
| Status | On time / Late / Not held |
Not yet confirmed — needs a follow-up walkthrough
- The actual output columns after clicking Generate (the required Location field couldn't be selected successfully during the testing attempted so far — needs a manual pass to complete a real Generate run).
- The exported CSV file format.
Execution Report and Usage Reporting (2 other sub-pages in the Reports section) have since been checked and documented — see Generating and exporting reports.