DocsCustom Events
Custom Events
Log app-specific events alongside the automatic session, network, and crash data BugsPulse already captures — they show up in the session timeline and on crash reports for context.
track()
Call track(name, properties?) anywhere after init() has run. Events are queued with the rest of the session data and flushed on the SDK's normal interval — no extra network calls to manage yourself.
# React Native
import BugsPulse from "@bugspulse/react-native";
BugsPulse.track("checkout_started", {
cartValue: 42.5,
itemCount: 3,
plan: "pro",
});# Flutter
import 'package:bugspulse/bugspulse.dart';
BugsPulse.track('checkout_started', {
'cartValue': 42.5,
'itemCount': 3,
'plan': 'pro',
});Arguments
| Argument | Type | Description |
|---|---|---|
name | string | Required. The event name, e.g. "checkout_started". |
properties | object | Optional key/value metadata attached to the event. |
Where events show up
Custom events appear inline in the session timeline in the BugsPulse dashboard, in the order they were tracked relative to network requests, touches, and the eventual crash (if any) — useful for reconstructing exactly what a user did leading up to an issue. If you want to be notified when specific conditions happen, see alerting.