Skip to content
Dashboard

Analytics

Installing the SDK is enough to start collecting link data. Clicks, installs, and attribution are tracked without any extra calls. You read the results in three dashboard views: Overview, Links, and Events.

The click and install flow produces these metrics on its own:

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

All three views share the same filters, that is selected app, platform, and date range, so numbers stay comparable when you move between them.

Analytics can also be delivered to your own endpoint on a schedule. See Webhooks.

Overview summarizes performance on one page. It shows four things:

  • link trend
  • organic vs non-organic install attribution
  • top event distribution
  • retention comparison

For cohort and N-day methodology, see Retention.

Link-level diagnostics: day-by-day link stats, plus a breakdown by path and query parameter. Use it to compare campaign routes and see where clicks and matches come from.

Smart banner taps are recorded like any other click. They carry utm_source=smart_banner, a utm_campaign of your choosing, and a dtb parameter identifying the banner, so all three appear in the parameter breakdown.

The same figures are available over HTTP, with pagination and filtering, through Export Analytics.

For the redirect and matching behavior behind these metrics, see Click Handling & Redirect Flow.

SDK event activity in the selected window:

  • total event count
  • timeline trends per event name
  • drill-down tables for event totals and individual occurrences

Every install is labeled by where it came from, which is what makes campaign effectiveness measurable:

  • Non-organic — the install was attributed to a specific click on a Detour link.
  • Organic — no prior link interaction was detected.

Automatic tracking covers the link funnel. To track later actions, for example sign-ups or purchases, log events yourself through the SDK’s analytics API.

If you are still setting up the 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");

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

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

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.