Screen tracking

1. Per-screen triggers — screen_viewed:/checkout automatically fires when the user lands on /checkout, so you can wire a survey to any path without adding trigger() calls everywhere.
2. Screen map in the dashboard — shows which paths exist, ordered by visit count.

​

Expo Router

import { Stack } from "expo-router";
import { InsitoProvider, useInsitoScreenTracking } from "@insito/react-native";

export default function RootLayout() {
  useInsitoScreenTracking();
  return (
    <InsitoProvider>
      <Stack />
    </InsitoProvider>
  );
}

• The hook reads usePathname() from expo-router.
• Each new (non-duplicate) pathname is recorded via MicroSurvey.recordScreenVisit(pathname).
• If the user has been identified, the SDK also fires a trigger named screen_viewed:<pathname> — fire-and-forget, swallowing errors. This means the dashboard can target a survey to a specific screen without your app shipping any new code.

​

React Navigation

import { NavigationContainer } from "@react-navigation/native";
import { MicroSurvey } from "@insito/react-native";

<NavigationContainer onStateChange={MicroSurvey.onNavigationStateChange}>
  ...
</NavigationContainer>

​

Manual screen recording

import { MicroSurvey } from "@insito/react-native";

useEffect(() => {
  MicroSurvey.recordScreenVisit("home");
}, []);

​

Data flow

​

Viewing screens in the dashboard

• Audit your information architecture (which screens are users actually using?).
• Target a survey to a specific path — paste the path into a survey’s trigger field with the screen_viewed: prefix, e.g. screen_viewed:/checkout/success.
• Spot dark corners — screens with low visit counts that aren’t marketing assumed dead-ends.

​

Limits and gotchas

• Paths are stored verbatim. If your route has dynamic params (/products/[id]), Expo Router gives you the templated form, not the literal — good. If you’re using React Navigation with manual params, the screen name omits them — also good.
• Each flush sends at most 200 paths (POST /v1/sdk/screen-map), so keep screen names bounded — collapse dynamic segments to templated forms (/products/[id]) rather than literal ids to avoid an unbounded path set.
• The hook is a no-op if expo-router isn’t installed. You’ll see one debug warning in development, then silence.