Event dictionary
The settings behind your events, in one table: what each one is, who owns it, and the one name it counts under.
Dashboard → Events → Manage → All events. One row per event name, with its type, volume (as a share of everything captured), last-seen time and whether it's being recorded. To see what an event's numbers look like, use the Events tab instead.
Event names are free text, so Manage is also where you keep them tidy: merge look-alike names into one, pick your key events, and watch problems with incoming events for what the server refused or flagged.
Two kinds of event:
- Automatic events: the ones the SDK and Fictura send without being asked. The app lifecycle (
first_open,app_open,app_backgrounded,app_updated,screen_viewed,screen_closed,element_tapped,rage_tap,dead_tap), the paywall and purchase events below, and the billing events Fictura writes from your RevenueCat webhook. - Your events: anything you send with
logEvent()from the app or from your server. Add one under Add an event you plan to send (the name is lowercased, spaces become underscores) and it shows as waiting for data until the first one arrives.
Every event carries a status (success, failure or info) and a source (frontend, backend, or webhook, which 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 stopping or sampling it is the fix.
Filters
- All lists every event that is neither hidden nor archived. Verified, Hidden and Archived show those on their own.
- Show automatic events is on by default. Switch it off to list only your own events.
- Under each row you may see a role (activation, conversion, value moment), Nothing in 7 days (seen before, but not lately), Nothing in 90 days, and the owner.
- Names merged into another one are listed under the name they now count as, each with an Unmerge button.
An event's settings
Click a row, or Manage on an event's own page, to open its settings.
- What it means: a description, tags, an owner (a person or team to ask), and three switches. Verified means reviewed and trusted; Hidden takes it out of the Events list. The two are exclusive: verifying an event un-hides it and the other way round. Archived keeps the event and its history but takes it out of the list and the pickers.
- Required properties: the properties the event should always carry, each with a type (
string,number,boolean,object,array). An event that arrives without one, or with the wrong type, is still stored and counted under problems with incoming events. - Sampling and Recording: see capture control.
- History: every change to the settings, field by field, with who made it and when. Kept forever.
Property descriptions are on the event's own page, under What it carries: written once, and shown wherever the key appears.
Billing events
Fictura writes these from your RevenueCat webhook (source: webhook). The vendor's own words are kept as properties: provider (revenuecat), raw_type (RevenueCat's event type) and raw_reason (its cancel or expiration reason, as sent).
| Event | When |
|---|---|
trial_started | A free trial began. |
trial_converted | The trial's first paid charge. |
trial_cancelled | Auto-renew turned off during a trial; the trial runs to its end. |
trial_expired | A trial ended without converting. |
subscription_started | A paid subscription began with no trial. is_resubscribe: true when the user had an earlier one that expired. |
subscription_renewed | A paid period renewed. Carries renewal_number and is_billing_recovery. |
subscription_cancelled | Auto-renew turned off; access continues to expires_at. |
subscription_uncancelled | Auto-renew turned back on. |
subscription_expired | Access ended. |
subscription_refunded | The store refunded the purchase. |
refund_reversed | A refund was taken back. |
billing_issue | A charge failed. Carries in_grace_period and grace_period_expires_at. |
price_increase_pending / price_increase_accepted | The user must consent to a price rise / did. |
entitlement_granted | A temporary entitlement (grant_type: temporary). |
subscription_paused, subscription_extended, subscription_product_changed, subscription_transferred, non_renewing_purchase | As RevenueCat reports them. |
webhook_test | RevenueCat's test ping. Shows the webhook works; never counted as revenue. |
subscription_event | Anything else RevenueCat sends. |
Every billing event carries, when RevenueCat sends it: product_id, store, environment, period_type, price_usd (the price in USD), price_local and currency (the price in the currency the user paid in), offer_type, cancel_reason / expiration_reason (lowercased), expires_at, purchased_at, external_event_id, and the paywall that sold it (placement, paywall_id, variant_id, campaign_id) when attribution found it. The old price key is still sent for one release.
Paywall and purchase events
From @fictura/sdk 0.22, every paywall (block, template, flow and served designs) logs the same names. Each one carries the placement block: placement, paywall_id, paywall_version, campaign_id, audience_id, experiment_id, variant_id, presented_by, paywall_session_id (one id per showing) and screen.
| Event | When | Properties |
|---|---|---|
paywall_shown | The paywall is on screen. | |
paywall_screen_viewed | Each screen of a flow paywall. | screen_index |
paywall_product_selected | The user picks a plan. | product_id, package_id, previous_product_id, is_default |
paywall_interacted | Another control, like the trial switch. | component_type, component_name, component_value |
paywall_cta_tapped | The buy button. | package_id |
purchase_started | The purchase is sent to the store. | attempt_id, product_id, package_id, offer_type |
purchase_completed | The store confirmed it (status success only). | attempt_id, product_id, transaction_id, period_type, price_local, currency, is_trial, latency_ms |
purchase_cancelled | The user closed the store sheet. | attempt_id, product_id |
purchase_failed | An error or a pending payment (status failure). | attempt_id, product_id, outcome, error_code, error_domain |
restore_started | Restore tapped. | |
restore_completed | The restore finished. | restored (false when there was nothing to restore) |
restore_failed | The restore threw. | error |
paywall_load_failed | The paywall could not draw. | stage (config, webview, products, template), error, fallback_used |
paywall_dismissed | The paywall is gone, once per showing. | close_reason, result (purchased, restored, declined), time_on_paywall_ms |
paywall_page_viewed | A Studio paywall moved to another of its screens (0.23). | index |
paywall_webview_crashed | The webview process died and the paywall is being brought back (0.23). | reason, attempt |
paywall_survey_answered | The user answered a close or post-purchase survey (0.23). | survey, question, answer, other_text |
paywall_survey_skipped | The user skipped that survey (0.23). | survey |
attempt_id ties one purchase attempt's events together.
A served design's own track() calls arrive as paywall_web_<event>, so a page can never send a revenue event. A short list keeps one canonical name, with source: "web" added: paywall_screen_viewed, paywall_page_viewed, paywall_product_selected (also from paywall_plan_selected), paywall_interacted (from paywall_trial_toggled), and exit_offer_shown, exit_offer_accepted and exit_offer_declined. A Studio paywall's paywall_action_unsupported is not on that list, so it arrives as paywall_web_paywall_action_unsupported.
Other SDK events
| Event | When |
|---|---|
placement_triggered | A placement was evaluated. Carries placement, result, campaign_id, audience_id, experiment_id, variant_id and paywall_id. |
paywall_presentation_request | The SDK decided whether to present. Carries placement, status (presentation, no_presentation, timeout) and status_reason. |
web_checkout_opened / web_checkout_open_failed | The web checkout opened, or could not (status failure). |
onboarding_started, onboarding_step_viewed, onboarding_question_answered, onboarding_completed, onboarding_skipped, onboarding_template_unsupported | From GrowthOnboarding. A served flow's own events arrive as onboarding_web_<event>. |
$opt_in | The user opted back in to tracking. |
$abnormal_exit | The last run died with no crash report. |
$ota_emergency_launch | expo-updates fell back to the embedded bundle. |
Renamed events
These names changed. You do not need to do anything for your history: Fictura counts the old name under the new one when it reads (aliases), and stored events are never rewritten. Update anything of your own that matches on names (exports, your own webhook handlers, saved queries).
| Old name | New name |
|---|---|
subscription_renewed for a trial's first charge | trial_converted |
subscription_cancelled with cancel_reason: CUSTOMER_SUPPORT | subscription_refunded |
subscription_cancelled during a trial | trial_cancelled |
subscription_expired for a trial | trial_expired |
subscription_event for RevenueCat REFUND_REVERSED, PRICE_INCREASE_CONSENT_*, TEMPORARY_ENTITLEMENT_GRANT, TEST | refund_reversed, price_increase_pending / price_increase_accepted, entitlement_granted, webhook_test |
purchase_succeeded | purchase_completed |
purchase_completed with status failure | purchase_failed |
purchase_attempted | purchase_started |
paywall_restore_tapped, restore_tapped | restore_started |
paywall_restore_succeeded, paywall_restore_none, restore_none_found | restore_completed |
paywall_restore_failed | restore_failed |
paywall_close_tapped | paywall_dismissed |
paywall_step_viewed | paywall_screen_viewed |
paywall_plan_selected | paywall_product_selected |
paywall_trial_toggled | paywall_interacted |
registration_completed | signup_completed |
paywall_template_unsupported | paywall_load_failed with stage: template |
paywall_web_paywall_page_viewed | paywall_page_viewed |
The billing rows above change only for events written after the switch; the same reader accepts both names, so churn states, the funnel and cohorts count old and new rows alike.
Four rows are not aliases, so history under the old name stays under it and only new events use the new one: paywall_close_tapped (House AI's older paywall logged both for one close, so merging would count it twice), paywall_template_unsupported, purchase_completed with status failure, and paywall_web_paywall_page_viewed. A paywall's Analytics tab in the Studio reads both page-view names.
Reading the Events tab
See what people do in your app: activity over time, every event on its own page, screens, taps, broken taps, sessions and devices.
Aliases and look-alike names
One name per thing: merge names that mean the same event, see the ones Fictura suggests, and undo any of it. Nothing stored is rewritten.