Events & collected records

Events

As the widget flow progresses, events are generated. An event is an immutable record of an action that has definitively occurred in the past. Each event contains information about what happened, when it occurred, the widget ID within the flow, session, pageload, and lead IDs, as well as an associated payload.

Events can be found in the Results tab or retrieved via the public API. Note that events may be delivered with a slight delay.

Below is a list of available events:

Name	Payload	Description
Widget shown	Load time (ms) Page URL Is lazy loaded?	The event represents a widget shown. A "show" refers to an actual visual display — for example, with lazy loading enabled, the event will not be triggered until the widget enters the viewport.
Widget touched	After time (ms) - the time from initialization to first interaction	The event represents a touch or interaction with the widget. This can include anything from focusing on an input field to clicking a button or other user actions.
Finished	Time taken (ms) - the time from initialization to finish	The event represents the successful completion of a widget. Completion occurs when the user reaches a state where there are no remaining widget flow nodes to process — either by reaching the end of the flow or landing on a dead-end node (e.g., a View node without a button).
Error thrown	Error - error type from the list Message - additional informarion	The event represents a widget error. You can find detailed explanations for each error type on the errors page.
Redirected	Destination URL - url after redirect	The event represents a redirect made by Redirect widget flow node.
Record collected	Record ID - collected record ID	The event represents a successful record collection made by Collect widget flow node. You can inspect collected record on the Results page.
AI prompted	Input - model input (truncated to 256 chars) Output - model output (truncated to 256 chars) Tokens - tokens spent on generation	The event represents a successful prompt made by AI prompt widget flow node.
HTTP requested	Status code - response HTTP status code Duration - request duration Result - response mapped with Response Map (if any) (truncated to 256 chars) Request ID - request ID for debugging	The event represents a HTTP request made by HTTP request widget flow node.
Email sent	No payload	The event represents a sent email by Email widget flow node.

Collected Records

In addition to events, widget flows may generate special records called collected records. These records are produced exclusively by the Collect widget flow node. Like events, each record includes ownership and ID metadata. However, instead of a payload, it contains data configured in the Collect node.

These records are also accessible from the Results tab and can be retrieved using the public API.

Each Collect widget flow node is assigned a partition field, which helps differentiate between groups of collected records. For example, if your widget flow includes multiple Collect nodes with different data formats, it's a good idea to assign different partitions to avoid mixing heterogeneous data.

By default, each Collect node is automatically assigned a randomly generated partition upon creation (or duplication), such as Clever Peacock 1234. You may change this value at any time to suit your organizational needs.

INFO

Previously collected records will not be updated if the partition value is changed.