Mobile funnel tracking

Measure one complete attempt

An attempt starts when the entire first required step is satisfied. That event starts the conversion window and supplies cohort properties. An unfinished first group is not a started attempt; use separate steps to measure losses within the group.

Create up to 20 required conversion steps and 30 total steps. Choose Attempts in the funnel editor and set the property carrying your attempt ID. Existing funnels continue counting visitors.

Send one opaque attempt ID on every required event, including completion. Keep it when resuming across sessions and replace it when restarting. Missing IDs cannot advance the funnel. A repeated screen requires a new event.

Use original occurrence timestamps for offline events. Equal timestamps require distinct increasing values in the configured sequence property to prove step order. Reuse the same ingestion dedupeKey for delivery retries when sending events through the tracking API.

Set cohort properties on the event that completes the first required step. Configure up to three properties, such as flow version, app version, and paywall variant, to compare their combinations. Missing entry values remain Unknown even if a later event supplies them.

Assign paywall variants before the journey starts to compare end-to-end conversion fairly. An app upgrade during a resumed attempt stays in its entry version cohort. Later conflicting values are reported without moving the attempt.

The reporting period selects attempts by their first required step. Completion can occur after the reporting period within the saved conversion window. Pending attempts have time remaining; confirmed drop-off counts only expired incomplete attempts.

Filter and compare entry cohorts, inspect each transition, and export all matching cohorts. Rates with no denominator show no data. Retained history may be incomplete after deletion or partial imports. Attempt reports do not attribute revenue.

Provider events need an explicit matching attempt ID and a verified visitor link. A shared customer ID alone does not prove that a payment belongs to the same attempt.

After entry, an event with a sequence number no greater than the last accepted number is skipped. Later valid events can continue the attempt. If tied starting events have no usable order and disagree on a cohort value, that value stays Unknown; agreeing values are kept. Ordering issues are reported.

Exports include pending attempts after each step and median completion time in minutes for each result group. A group with no completed attempts has no median completion time.

A mobile funnel combines three types of steps: screen views, goal events, and transaction events synced from RevenueCat. React Native can capture screens through its navigation callbacks; native iOS, Android, and Flutter apps call trackScreen from their navigation lifecycle. You can mix all three in one funnel.

Anonymous tracking and identity linking

1await tracker.track('account_created');23await tracker.track('profile_completed', {4  had_avatar: true,5  fields_filled: 4,6});

1await Purchases.logIn(user.id);2await tracker.identify(user.id);34// Before sign-out on a shared device5await tracker.reset();