Skip to main content

Analytics

The Detour platform provides a comprehensive analytics system that automatically tracks user engagement and link performance. By integrating the SDK, you gain access to deep insights into how users interact with your application. Data is available in three dashboard views: Overview, Links, and Events.

What is tracked automatically​

From platform click/install flow:

  • Clicks: counted from recorded click beacons.
  • Installs via link: installs attributed to a matched click.
  • Fallbacks: clicks that ended on non-mobile fallback flow.
  • Organic vs Non-Organic installs: based on whether install was matched to a click.

Analytics views in the dashboard​

All analytics views are scoped by the same core filters (selected app, platform, and date range), so comparisons across views stay consistent.

Overview​

Overview is the fastest way to read overall performance. It combines link trend data, organic vs non-organic install attribution, top event distribution, and retention comparison in one place. Use this view first when you need a quick health check before drilling into details.

For cohort and N-day retention methodology details, see Retention system.

Links view is focused on link-level diagnostics. It shows day-by-day link stats plus path and query-parameter breakdowns, so you can compare campaign routes and understand where clicks and matches are coming from.

For redirect and matching behavior that drives these metrics, see Click Handling & Redirect Flow.

Events​

Events view is focused on SDK event activity. It includes total event count, timeline trends by event name, and drill-down tables for event totals and occurrences in the selected filter window.

Organic vs. Non-Organic Attribution​

Detour distinguishes between different installation sources to help you measure the effectiveness of your campaigns:

  • Non-Organic: Installations that the system successfully attributed to a specific click on a Detour link.
  • Organic: Standard installations where no prior link interaction was detected by the SDK.

Manual event tracking from SDKs​

Beyond automatic tracking, you can log specific user behaviors using the analytics API. This allows you to track the user journey through your conversion funnel.

Use the analytics API in your SDK:

If you are still setting up integration, start with Getting Started with Detour.

import { DetourAnalytics, DetourEventNames } from "@swmansion/react-native-detour";

DetourAnalytics.logEvent(DetourEventNames.Login);
DetourAnalytics.logEvent(DetourEventNames.Purchase, { value: 9.99, currency: "USD" });
DetourAnalytics.logRetention("day_7_return");

Retention system​

Detour retention is event-based. It is calculated from SDK calls to logRetention("<event_name>"), grouped by retention event name.

Data model​

  • Retention events are stored in analytics as a dedicated retention stream.
  • They are tied to event name, device, time, and platform.
  • Retention data is not mixed into regular event charts like Top Events and Events timeline.

Cohorts and N-day logic​

  • A cohort is the group of devices that triggered a given retention event for the first time in the selected date range.
  • Day 0 is the first occurrence day, and later points (Day 1, Day 2, ...) show return behavior on following days.
  • Retention is tracked up to 30 days (Day 0 to Day 30).
  • Future dates are excluded to avoid artificial 0% drops on incomplete days.
  • Platform filtering works the same way as in other analytics views.

Metrics​

Retention reporting shows:

  • how many cohort devices returned on a given day,
  • how large the original cohort was,
  • and the resulting retention percentage.

When multiple cohorts are combined on one chart line, Detour uses weighted aggregation so larger cohorts have proportionally higher impact.

We are Software Mansion.

Hire us