Fictura
Events

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.

Event names drift. One release sends purchase_succeeded, the next purchase_completed; one screen logs PaywallShown, another paywall_shown. Counted apart, each looks half as big as it is. Fictura lets you say they are one event.

How a merge works

A merge says "count old_name as new_name". From then on, every read groups the old name under the new one: the events list, definitions, breakdowns, the tap matrix, actions, the overview, the funnel, churn states and cohorts, and the tracking plan Hawkings and the MCP tools read.

  • Nothing is rewritten. Raw events keep the name they were sent with. A merge changes how they are counted, not what is stored, so it applies to your whole history at once and can be undone at any time.
  • One hop. A name merges into a name that is not itself merged, and a name other names are merged into cannot itself be merged. Fictura refuses a chain (a → b → c) or a loop.
  • The list shows it. A merged name is listed under the name it counts as, with an Unmerge button.

Built-in aliases

These apply to every app, because the SDK and House AI used the old names before the canonical names:

Old nameCounts as
purchase_succeededpurchase_completed
purchase_attemptedpurchase_started
paywall_restore_tapped, restore_tappedrestore_started
paywall_restore_succeeded, paywall_restore_none, restore_none_foundrestore_completed
paywall_restore_failedrestore_failed
paywall_step_viewedpaywall_screen_viewed
paywall_plan_selectedpaywall_product_selected
paywall_trial_toggledpaywall_interacted
registration_completedsignup_completed

Your own merges win over a built-in. Unmerge on a built-in alias opts that one name out for your app.

paywall_close_tapped is deliberately not a built-in alias of paywall_dismissed: House AI's older paywall logged both for the same close, so merging them would count every close twice.

Look-alike names

Dashboard → Events → Manage → Look-alike names lists groups of names that are probably the same event, from the last 30 days. Names are grouped when they:

  • are equal once lowercased with everything but letters and digits removed (PaywallShown, paywall_shown, paywall-shown), or
  • are within two edits of each other after that (purchase_complete, purchase_completed), or
  • point at the same built-in alias target.

A mixed-case name with no look-alike (tool_paywalls_ON) is listed on its own, suggesting its lower-case form.

Each group shows every name with its events, users and last seen time, and suggests one to keep: a built-in canonical name if the group has one, otherwise the name with the most events. Pick another if you prefer, then Merge into …. An Undo appears straight after and puts every name back as it was.

Every merge and unmerge is recorded in the event's History tab, with who made it and when.

Dashboard only

Look-alikes and merges run on the dashboard's own endpoints (GET /api/v1/stats/events/lookalikes, PATCH /api/v1/stats/events/definitions/:name with merged_into), which take a dashboard session, not an SDK or API key. They are not meant for server integrations.

On this page