Contentful Personalization & Analytics

Optimization React Native SDK

The Optimization React Native SDK implements functionality specific to React Native applications, based on the Optimization Core Library. This SDK is part of the Contentful Optimization SDK Suite.

Getting Started

Install using an NPM-compatible package manager, pnpm for example:

pnpm install @contentful/optimization-react-native @react-native-async-storage/async-storage
Copy

For offline support (recommended), also install:

pnpm install @react-native-community/netinfo
Copy

Import the Optimization React Native SDK; both CJS and ESM module systems are supported, ESM preferred:

import { OptimizationReactNativeSdk } from '@contentful/optimization-react-native'
Copy

Configure and initialize the Optimization React Native SDK:

const optimization = await OptimizationReactNativeSdk.create({
  clientId: 'your-client-id',
  environment: 'main',
})
Copy

Reference Implementation

• React Native: Example application that displays personalized content, with builds targeted for both Android and iOS

Configuration

Top-level Configuration Options

Configuration method signatures:

• getAnonymousId: () => string | undefined

Analytics Options

Configuration method signatures:

• beaconHandler: (url: string | URL, data: BatchInsightsEventArray) => boolean

Event Builder Options

Event builder options should only be supplied when building an SDK on top of the Optimization React Native SDK or any of its descendent SDKs.

The channel option may contain one of the following values:

• web
• mobile
• server

Configuration method signatures:

• getLocale: () => string | undefined

• getPageProperties:

  () => {
    path: string,
    query: Record<string, string>,
    referrer: string,
    search: string,
    title?: string,
    url: string
  }
  Copy

• getUserAgent: () => string | undefined

Fetch Options

Fetch options allow for configuration of a Fetch API-compatible fetch method and the retry/timeout logic integrated into the Optimization API Client. Specify the fetchMethod when the host application environment does not offer a fetch method that is compatible with the standard Fetch API in its global scope.

Configuration method signatures:

• fetchMethod: (url: string | URL, init: RequestInit) => Promise<Response>
• onFailedAttempt and onRequestTimeout: (options: FetchMethodCallbackOptions) => void

Personalization Options

Component Tracking

Important: When we refer to "component tracking," we're talking about tracking Contentful entry components (content entries in your CMS), NOT React Native UI components. The term "component" comes from Contentful's terminology for personalized content entries.

The SDK provides two semantic components for tracking different types of Contentful entries:

<Personalization /> - For Personalized Entries

Use this component to track Contentful entries that can be personalized (have nt_experiences field). It automatically:

• Resolves the correct variant based on user profile and active personalizations
• Provides the resolved entry via render prop
• Tracks component views when visibility and time thresholds are met

<Analytics /> - For Non-Personalized Entries

Use this component to track standard Contentful entries you want analytics on (articles, etc.). It:

• Tracks any Contentful entry without personalization
• Uses a simple children pattern (no render prop needed)
• Same visibility and time tracking as <Personalization />

Both components track when an entry:

• Is at least 80% visible in the viewport (configurable via threshold prop)
• Has been viewed for 2000ms (2 seconds, configurable via viewTimeMs prop)

ScrollView vs Non-ScrollView Usage

The tracking components work in two modes:

Inside ScrollView (Recommended for Scrollable Content)

When used inside a <OptimizationScrollProvider>, tracking uses the actual scroll position and viewport dimensions:

<OptimizationScrollProvider>
  <Personalization baselineEntry={entry}>
    {(resolvedEntry) => <HeroComponent data={resolvedEntry} />}
  </Personalization>
  <Analytics entry={productEntry}>
    <ProductCard data={productEntry.fields} />
  </Analytics>
</OptimizationScrollProvider>
Copy

Benefits:

• Accurate viewport tracking as user scrolls
• Works for content that appears below the fold
• Triggers when component scrolls into view

Outside ScrollView (For Non-Scrollable Content)

When used without <OptimizationScrollProvider>, tracking uses screen dimensions instead:

<Personalization baselineEntry={entry}>
  {(resolvedEntry) => <FullScreenHero data={resolvedEntry} />}
</Personalization>

<Analytics entry={bannerEntry}>
  <Banner data={bannerEntry.fields} />
</Analytics>
Copy

Note: In this mode, scrollY is always 0 and viewport height equals the screen height. This is ideal for:

• Full-screen components
• Non-scrollable layouts
• Content that's always visible when the screen loads

Custom Tracking Thresholds

Both components support customizable visibility and time thresholds:

<Personalization
  baselineEntry={entry}
  viewTimeMs={3000}      // Track after 3 seconds of visibility
  threshold={0.9}        // Require 90% visibility
>
  {(resolvedEntry) => <YourComponent data={resolvedEntry.fields} />}
</Personalization>

<Analytics
  entry={entry}
  viewTimeMs={1500}      // Track after 1.5 seconds
  threshold={0.5}        // Require 50% visibility
>
  <YourComponent />
</Analytics>
Copy

Key Features:

• Tracks only once per component instance
• Works with or without OptimizationScrollProvider (automatically adapts)
• Default: 80% visible for 2000ms (both configurable)
• Tracking fires even if user never scrolls (checks on initial layout)
• <Personalization /> uses render prop pattern to provide resolved entry
• <Analytics /> uses standard children pattern

Manual Analytics Tracking

You can also manually track events using the analytics API:

import { useOptimization } from '@contentful/optimization-react-native'

function MyComponent() {
  const optimization = useOptimization()

  const trackManually = async () => {
    await optimization.trackComponentView({
      componentId: 'my-component',
      experienceId: 'exp-456',
      variantIndex: 0,
    })
  }

  return <Button onPress={trackManually} title="Track" />
}
Copy

OptimizationRoot

OptimizationRoot is the recommended way to set up the SDK. It combines OptimizationProvider with optional preview panel functionality:

import {
  OptimizationReactNativeSdk,
  OptimizationRoot,
  OptimizationScrollProvider,
} from '@contentful/optimization-react-native'
import { createClient } from 'contentful'

const contentfulClient = createClient({
  space: 'your-space-id',
  accessToken: 'your-access-token',
})

const optimization = await OptimizationReactNativeSdk.create({
  clientId: 'your-client-id',
  environment: 'your-environment',
})

function App() {
  return (
    <OptimizationRoot
      instance={optimization}
      previewPanel={{
        enabled: __DEV__, // Only show in development
        contentfulClient: contentfulClient,
      }}
    >
      <OptimizationScrollProvider>{/* Your app content */}</OptimizationScrollProvider>
    </OptimizationRoot>
  )
}
Copy

Preview Panel

When previewPanel.enabled is true, a floating action button appears that opens the preview panel. The panel allows developers to:

• Browse and override audience membership
• Select specific variants for experiences
• View current profile information
• Test personalizations without modifying actual user data

<OptimizationRoot
  instance={optimization}
  previewPanel={{
    enabled: true,
    contentfulClient: contentfulClient,
    fabPosition: { bottom: 50, right: 20 }, // Optional: customize button position
    showHeader: true, // Optional: show header in panel
    onVisibilityChange: (isVisible) => {
      console.log('Preview panel visible:', isVisible)
    },
  }}
>
  {/* ... */}
</OptimizationRoot>
Copy

Live Updates Behavior

By default, <Personalization /> components lock to the first variant they receive. This prevents UI "flashing" when user actions (like identifying or taking actions that change audience membership) cause them to qualify for different personalizations mid-session.

Default Behavior (Recommended)

// User sees Variant A on initial load
<Personalization baselineEntry={heroEntry}>
  {(resolvedEntry) => <Hero data={resolvedEntry.fields} />}
</Personalization>

// Even if the user later qualifies for Variant B (e.g., after identify()),
// they continue to see Variant A until the component unmounts
Copy

This provides a stable user experience where content doesn't unexpectedly change while the user is viewing it.

Enabling Live Updates

There are three ways to enable live updates (immediate reactions to personalization changes):

1. Preview Panel (Automatic)

When the preview panel is open, all <Personalization /> components automatically enable live updates. This allows developers to test different variants without refreshing the screen:

<OptimizationRoot instance={optimization} previewPanel={{ enabled: true, contentfulClient }}>
  {/* All Personalization components will live-update when panel is open */}
</OptimizationRoot>
Copy

2. Global Setting via OptimizationRoot

Enable live updates for all <Personalization /> components in your app:

<OptimizationRoot instance={optimization} liveUpdates={true}>
  {/* ... */}
</OptimizationRoot>
Copy

3. Per-Component Override

Enable or disable live updates for specific components:

// This component will always react to changes immediately
<Personalization baselineEntry={dashboardEntry} liveUpdates={true}>
  {(resolvedEntry) => <Dashboard data={resolvedEntry.fields} />}
</Personalization>

// This component locks to first variant, even if global liveUpdates is true
<Personalization baselineEntry={heroEntry} liveUpdates={false}>
  {(resolvedEntry) => <Hero data={resolvedEntry.fields} />}
</Personalization>
Copy

Priority Order

The live updates setting is determined for a particular <Personalization/> component in this order (highest to lowest priority):

1. Preview panel open - Always enables live updates (cannot be overridden)
2. Component liveUpdates prop - Per-component override
3. OptimizationRoot liveUpdates prop - Global setting
4. Default - Lock to first variant (false)

React Native-Specific Defaults

The SDK automatically configures:

• Channel: 'mobile'
• Library: 'Optimization React Native SDK'
• Storage: AsyncStorage for persisting changes, consent, profile, and personalizations
• Event Builders: Mobile-optimized locale, page properties, and user agent detection

Persistence Behavior

AsyncStorage persistence is best-effort. If AsyncStorage write/remove calls fail, the SDK keeps running with in-memory state and retries persistence on future writes.

Structured cached values (changes, profile, personalizations) are schema-validated on load and access. Malformed JSON or schema-invalid values are automatically removed from in-memory cache and AsyncStorage.

Offline Support

The SDK automatically detects network connectivity changes and handles events appropriately when the device goes offline. To enable this feature, install the optional peer dependency:

pnpm install @react-native-community/netinfo
Copy

Once installed, the SDK will:

• Queue events when the device is offline
• Automatically flush queued events when connectivity is restored
• Flush events when the app goes to background (to prevent data loss)

No additional configuration is required - the SDK handles everything automatically.

How It Works

The SDK uses @react-native-community/netinfo to monitor network state changes. It prioritizes isInternetReachable (actual internet connectivity) over isConnected (network interface availability) for accurate detection.

If @react-native-community/netinfo is not installed, the SDK will log a warning and continue without offline detection. Events will still work normally when online.

Polyfills

The SDK includes automatic polyfills for React Native to support modern JavaScript features:

• Iterator Helpers (ES2025): Polyfilled using es-iterator-helpers to support methods like .toArray(), .filter(), .map() on iterators
• crypto.randomUUID(): Polyfilled using react-native-uuid to ensure the universal EventBuilder works seamlessly
• crypto.getRandomValues(): Polyfilled using react-native-get-random-values for secure random number generation

These polyfills are imported automatically when you use the SDK - no additional setup required by your app.