AutoNavTracking.tsx

/**
 * Automatic Navigation Tracking
 *
 * With `autoTrackNavigation`, the SDK emits a `screen_view` event every time the
 * user navigates — no manual per-screen calls. Because screen views flow through
 * the normal event pipeline, they're automatically attributed to the deep link
 * that drove the visit, so LinkForty can show an *attributed* screen-flow
 * funnel per campaign (which link → which screens → which events).
 *
 * Setup is one-time:
 *   1. Create a navigation ref with `createNavigationContainerRef()`.
 *   2. Pass it to BOTH `<NavigationContainer ref={...}>` and `LinkForty.init`.
 *   3. Set `autoTrackNavigation: true`.
 *
 * Apps that don't use React Navigation simply omit `navigationRef` — nothing
 * else changes and there is no required dependency.
 */

import React, { useEffect } from 'react';
import { Text, View } from 'react-native';
import {
  NavigationContainer,
  createNavigationContainerRef,
} from '@react-navigation/native';
import { createNativeStackNavigator } from '@react-navigation/native-stack';
import LinkForty from '@linkforty/mobile-sdk-react-native';

// A single ref shared between React Navigation and LinkForty.
export const navigationRef = createNavigationContainerRef();

const Stack = createNativeStackNavigator();

function HomeScreen() {
  return (
    <View>
      <Text>Home</Text>
    </View>
  );
}

function ProductScreen() {
  return (
    <View>
      <Text>Product</Text>
    </View>
  );
}

export default function App() {
  useEffect(() => {
    LinkForty.init({
      baseUrl: 'https://go.yourdomain.com',
      appToken: 'at_your_workspace_token', // attributes organic installs to your workspace
      // `true` = privacy-safe default: screen names only, no route params.
      // To capture specific non-PII params, opt in with an allow-list instead:
      //   autoTrackNavigation: { captureParams: ['productId', 'category'] },
      autoTrackNavigation: true,
      navigationRef, // <-- the same ref passed to NavigationContainer
      debug: __DEV__,
    }).catch((error) => {
      console.error('Failed to initialize LinkForty:', error);
    });
  }, []);

  return (
    <NavigationContainer ref={navigationRef}>
      <Stack.Navigator>
        <Stack.Screen name="Home" component={HomeScreen} />
        <Stack.Screen name="Product" component={ProductScreen} />
      </Stack.Navigator>
    </NavigationContainer>
  );
}

/**
 * Notes
 * -----
 * - `screen_view` events carry the active deep-link attribution + a session id,
 *   so re-engagement campaigns (a link tapped by an already-installed user) are
 *   attributed to the link they tapped — not their original install link.
 * - Route params are OFF by default (privacy-safe): only the screen name is sent.
 *   Opt in to specific non-PII params with an explicit allow-list:
 *   `autoTrackNavigation: { captureParams: ['productId'] }`. Only those keys'
 *   primitive values are captured (strings capped, objects/arrays dropped).
 * - Your custom events (e.g. `add_to_cart`, `purchase`) are attributed the same
 *   way — keep calling `LinkForty.trackEvent(...)` as usual.
 */