Fictura
Events

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.

Dashboard → Events. Pick a period at the top right: 24 hours, 7, 30 or 90 days. Every number on the tab follows it, and each one is compared with the same length of time just before.

Overview

The front page answers "what happened?" in a sentence, four numbers and a graph:

  • Events: how many arrived in the period.
  • People: how many different people did at least one thing.
  • Per person: events each, on average.
  • Worked: of the events that report success or failure, the share that succeeded.

Worth a look lists what deserves your attention, and links to where you can act on it: taps that did nothing, things that fail often, crashes, events that stopped arriving, and a value moment with too little data behind it. When nothing stands out, it isn't shown.

Did it work? lists events your app marks as a success or a failure, the ones failing most first. Add this to your own features with trackOutcome.

All events lists every event with a small trend, people, count and change. Search finds a name or its label. Events are grouped:

GroupWhat's in it
Your eventsWhat your own code sends.
MoneyTrials, subscriptions, purchases and restores.
PaywallsWho saw a paywall and what they did.
OnboardingHow people move through your onboarding.
App useOpens and screens.
TapsTaps, dead taps and rage taps.
ErrorsCrashes and errors. Issues groups these by cause.
Fictura systemHousekeeping events from the SDK and Fictura.

Events with nothing in the period are folded at the bottom, with when each was last seen. Hidden and archived ones are left out, and Manage lists them.

An event's own page

Click any event for its page:

  • Numbers: times it happened, people, per person, and when it was first and last seen.
  • Over time: a graph you can switch between count and people.
  • Did it work?: for an event that reports success or failure, how often it worked, the share that failed each day, the top error codes, and how long it usually takes when it sends duration_ms.
  • How it splits: bars for the event's own properties, app version, country, operating system, device, screen, language and where it was sent from. Split by something else covers any other property.
  • What it carries: every property, how often it's present and some example values, with your own properties apart from the ones added automatically. Each of your properties can have a description.
  • Latest events: the rows themselves, newest first. Open one to see everything it carried, and who sent it.

Values that look personal, like an email or a phone number, are masked until you press Show personal values.

Country is the person's latest known country, not where they were when the event happened.

Screens

Every screen, most viewed first, with its share of views, people and typical time: half of visits were shorter than that, half longer.

Screens are recorded automatically by the expo-router tracker. On anything else, call Growth.screen(name) when a screen appears.

Taps

What gets tapped, on which screen, with a filter by screen.

Taps are recorded automatically unless autocapture.captureTouches is off. Give an element a clear name with the fictura-label prop if its label isn't useful.

Broken taps

Two kinds of tap mean something went wrong:

  • Dead tap: someone tapped something that should respond, and within half a second nothing had happened.
  • Rage tap: someone tapped the same spot four or more times within a second.

The view shows how many of each, how many people hit them, what share of all taps they are, how that changes over time, and exactly where, worst first. Start at the top of the list.

Sessions

A session is one visit to your app. The view shows how many there were, their typical length, how many people left right away (one screen, under 10 seconds), and how many saw a paywall and paid in the same visit. Below that: how long sessions last, where they start and end, platform, app version and the latest sessions, each linking to that person.

Devices

What people use your app on: app version, system, device, country, language, time zone and network. It reads app opens, so someone who uses your app a lot doesn't count for more than someone who doesn't.

Details on every event

Add a detail like plan or user type once, and it rides along on everything your app sends. You can then split any event by it.

Growth.registerSuperProperties({ plan: "pro", user_type: "paying" });

These details are listed under Details sent with every event. Everything Fictura adds on its own is listed below them.

When a number is an estimate

A number with ≈ in front of it is an estimate, for one of two reasons:

  • The event is sampled. Only a share of devices send it, so its count is scaled back up. See sampling. People aren't scaled up: they are the people on devices that sent it.
  • The view read a sample. Screens, Taps and the standard breakdowns (app version, device and OS details, screen, language, source and country) are counted exactly, people included, from summaries Fictura keeps by the hour. An event's own properties and typical time on a screen are slow to read on very busy events, so past 10,000 events in the period Fictura reads 10,000 spread evenly across it. The view says when it did this. Shares hold up well, and the totals are scaled from them. People aren't shown for a sample, because they can't be scaled up.

An app just connected, or one that has just imported history, can read samples for a few hours while its summaries catch up.

The period's totals and graphs are always exact, apart from sampled events.

Manage

Manage, at the right of the tabs, holds the settings: key events, look-alike names, adding an event, the full list and problems with incoming events.

On this page