Fictura
Events

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).

EventWhen
trial_startedA free trial began.
trial_convertedThe trial's first paid charge.
trial_cancelledAuto-renew turned off during a trial; the trial runs to its end.
trial_expiredA trial ended without converting.
subscription_startedA paid subscription began with no trial. is_resubscribe: true when the user had an earlier one that expired.
subscription_renewedA paid period renewed. Carries renewal_number and is_billing_recovery.
subscription_cancelledAuto-renew turned off; access continues to expires_at.
subscription_uncancelledAuto-renew turned back on.
subscription_expiredAccess ended.
subscription_refundedThe store refunded the purchase.
refund_reversedA refund was taken back.
billing_issueA charge failed. Carries in_grace_period and grace_period_expires_at.
price_increase_pending / price_increase_acceptedThe user must consent to a price rise / did.
entitlement_grantedA temporary entitlement (grant_type: temporary).
subscription_paused, subscription_extended, subscription_product_changed, subscription_transferred, non_renewing_purchaseAs RevenueCat reports them.
webhook_testRevenueCat's test ping. Shows the webhook works; never counted as revenue.
subscription_eventAnything 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.

EventWhenProperties
paywall_shownThe paywall is on screen.
paywall_screen_viewedEach screen of a flow paywall.screen_index
paywall_product_selectedThe user picks a plan.product_id, package_id, previous_product_id, is_default
paywall_interactedAnother control, like the trial switch.component_type, component_name, component_value
paywall_cta_tappedThe buy button.package_id
purchase_startedThe purchase is sent to the store.attempt_id, product_id, package_id, offer_type
purchase_completedThe store confirmed it (status success only).attempt_id, product_id, transaction_id, period_type, price_local, currency, is_trial, latency_ms
purchase_cancelledThe user closed the store sheet.attempt_id, product_id
purchase_failedAn error or a pending payment (status failure).attempt_id, product_id, outcome, error_code, error_domain
restore_startedRestore tapped.
restore_completedThe restore finished.restored (false when there was nothing to restore)
restore_failedThe restore threw.error
paywall_load_failedThe paywall could not draw.stage (config, webview, products, template), error, fallback_used
paywall_dismissedThe paywall is gone, once per showing.close_reason, result (purchased, restored, declined), time_on_paywall_ms
paywall_page_viewedA Studio paywall moved to another of its screens (0.23).index
paywall_webview_crashedThe webview process died and the paywall is being brought back (0.23).reason, attempt
paywall_survey_answeredThe user answered a close or post-purchase survey (0.23).survey, question, answer, other_text
paywall_survey_skippedThe 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

EventWhen
placement_triggeredA placement was evaluated. Carries placement, result, campaign_id, audience_id, experiment_id, variant_id and paywall_id.
paywall_presentation_requestThe SDK decided whether to present. Carries placement, status (presentation, no_presentation, timeout) and status_reason.
web_checkout_opened / web_checkout_open_failedThe web checkout opened, or could not (status failure).
onboarding_started, onboarding_step_viewed, onboarding_question_answered, onboarding_completed, onboarding_skipped, onboarding_template_unsupportedFrom GrowthOnboarding. A served flow's own events arrive as onboarding_web_<event>.
$opt_inThe user opted back in to tracking.
$abnormal_exitThe last run died with no crash report.
$ota_emergency_launchexpo-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 nameNew name
subscription_renewed for a trial's first chargetrial_converted
subscription_cancelled with cancel_reason: CUSTOMER_SUPPORTsubscription_refunded
subscription_cancelled during a trialtrial_cancelled
subscription_expired for a trialtrial_expired
subscription_event for RevenueCat REFUND_REVERSED, PRICE_INCREASE_CONSENT_*, TEMPORARY_ENTITLEMENT_GRANT, TESTrefund_reversed, price_increase_pending / price_increase_accepted, entitlement_granted, webhook_test
purchase_succeededpurchase_completed
purchase_completed with status failurepurchase_failed
purchase_attemptedpurchase_started
paywall_restore_tapped, restore_tappedrestore_started
paywall_restore_succeeded, paywall_restore_none, restore_none_foundrestore_completed
paywall_restore_failedrestore_failed
paywall_close_tappedpaywall_dismissed
paywall_step_viewedpaywall_screen_viewed
paywall_plan_selectedpaywall_product_selected
paywall_trial_toggledpaywall_interacted
registration_completedsignup_completed
paywall_template_unsupportedpaywall_load_failed with stage: template
paywall_web_paywall_page_viewedpaywall_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.

On this page