Event dictionary
Every event your app has ever sent, in one table — what it is, how often it fires, when it was last seen, and whether it's still being captured.
Dashboard → Events. One row per event name, with its type, volume (as a share of everything captured), last-seen time, and its capture toggle. Event names are free text — the pipeline accepts any name — but two kinds get special treatment:
- Auto events — the ones the SDK and platform emit without being asked:
app_open,first_open,screen_viewed,screen_closed,element_tapped,session_started,notification_received,cancel_survey_answered, and the billing family (trial_started,subscription_started,subscription_renewed,subscription_cancelled,subscription_uncancelled,subscription_expired,billing_issue,subscription_event). - Custom events — anything you send with
logEvent()from the app or from your server. Declare one from the dictionary (name is lowercased, spaces become underscores) and it shows as awaiting data until the first occurrence arrives.
Every event carries a status — success, failure, or info — and a source — frontend, backend, or webhook (the last is reserved for Fictura's own billing events). The success/failure pair is what the generation-health view is built from.
Reading the volume column
Volume is each event's share of everything captured. A single event above ~40% of total volume is flagged — it usually means a chatty auto-event is drowning the signal, and its capture toggle is the fix.