candu.sdk.
Common Events
Content events are generic events common to every type of content. Every SDK event includes a core set of identifiers. Depending on the event type, additional properties may be included.candu.sdk.content
Fired when a user views content on their screen. This event only triggers if the user has actually seen the content on their screen.Component Events
These are useful for tracking interactions. Component events always have anodeId associated with them. Note that components do not have identifiers as they’re a logical grouping of Nodes.
Component events have the following identifiers:
candu.sdk.content.interaction
A generic interaction event. This event is emitted by components likeButton, Link, Card and any other component where an interaction can be specified.
candu.sdk.dismiss
A generic dismiss events. This action is emitted byModal or Card when they are dismissed.
Checklists
candu.sdk.tutorial.checklist_group_complete
Event emitted once when all items in a Checklist have been completed. Includes the following additional properties:
Includes the checklist
title in the payload.
candu.sdk.tutorial.checklist_item_state_updated
Emitted when an individual checklist item’s state changes. Please note that event-driven Checklists do not emit this event. Includes the following additional properties:
Includes the checklist
title in the payload,
Flows
candu.sdk.flow_step
A Flow Step has been seen. This actions are emitted byFlowStepnodes when they are being displayed as part of a Flow.
Form
candu.sdk.form_submit
A Form has been submitted. TheformId will be included in the body, as well as an encoded payload of all the Form fields.