Fire Event
The Fire Event action triggers custom analytics events within your app. These events can be used for tracking user interactions, measuring feature usage, triggering workflows, or communicating with external analytics services.
📦 Properties
events
Array
✅
List of events to fire, each with name and optional payload
✅ Common Use Cases
Tracking user interactions and feature usage
Measuring conversion funnels and user journeys
Triggering custom workflows based on user actions
Sending data to external analytics platforms
Implementing event-driven architectures
A/B testing and feature flag implementations
⚙️ Default Behavior
By default:
Event Processing
All events in the array are fired sequentially
Analytics Integration
Events are sent to configured analytics handlers
Payload Evaluation
Event payloads are processed as-is (no expression evaluation)
Error Handling
Continues processing remaining events if one fails
🛠️ How to Use

Add the action to a widget event (e.g., button tap, form submission)
Choose Fire Event from the action list
Add events to the
eventsarray with names and optional payloads
Event Name (name):
Required field that identifies the type of event
Should be descriptive and follow consistent naming conventions
Examples:
"button_clicked","form_submitted","feature_used"Used by analytics systems to categorize and track events
Event Payload (payload):
Optional field containing additional data about the event as a JSON object
Can include any relevant information (strings, numbers, booleans, arrays, nested objects)
Supports dynamic values using expressions (e.g.,
appState.currentUser)Used for detailed event analysis and segmentation
📊 Event Structure
Each event in the events array has the following structure:
Last updated