Event Types
- Silva, Carlos
Analytics events can be:
Triggered by the client-side, i.e. web or iOS/Android apps, also called User Interactions
Triggered by the server-side, also called Functional Events.
Client-side events
Client-side events capture user interactions that correspond to, in most cases, interactive UI components or patterns that are visible in the application. These allow us to:
Keep the list of events limited and intuitive.
Create micro funnels based on component-to-component interaction.
Quantify the overall error rate of the application and also the breakdown per flow, page, and component.
Standard user interaction events
Button | The user clicks/taps on a button. |
Card | The user clicks/taps on a card. |
Checkbox | The user checks/unchecks a checkbox. |
Chip | The user clicks/taps on a chip. |
Dropdown | The user clicks/taps on a dropdown. |
Error | An error is triggered after a user action. |
Input | The input field gets focused. |
Link | The user clicks/taps on a link. |
List Item | The user clicks/taps on an item in a list. |
Modal | A modal is displayed to the user. |
Navigation | The user clicks/taps on a navigation item. |
Number Input | The user clicks/taps on one of the interactive elements of the number input component: minus button, plus button or the number field. |
Paginate | The user clicks/taps on the pagination button. |
Page View | The user lands on a page (URL). |
Radio Button | The user clicks/taps on a radio button. |
Segmented Button | The user clicks/taps on a segmented button. |
Snackbar | A snackbar is displayed after a user action. |
Switch | The user clicks/taps on a switch. |
Tab | The user clicks/taps on a tab. |
Text Area | The text area gets focused. |
Standard user interaction event properties
See Attributes and properties to understand what event properties are.
Label | While the event defines the component, e.g. |
Path | The path URL after the domain, e.g. |
Type Exclusive property | Exclusive for lists to help better differentiate content like different reward cards by tier, or pages where we might have offers mixed with rewards. |
Server-side events
These are captured by the server-side. They are more limited than User Interaction events since they don’t know which UI component was used to trigger the event, but they are more reliable since they are only captured once a request has actually been processed by the RBI platform (while some User Interaction events may be lost in case the web/app loses connectivity).
Examples of server-side events are:
Sign Up Complete
Order Complete
Item Added to Cart
Offer Redeemed
Reward Redeemed