There are two ways to implement feature flags in React: 1. Using hooks. 2. Using the `` component. ### Method 1: Using hooks PostHog provides several hooks to make it easy to use feature flags in your React app. | Hook | Description | | --- | --- | | `useFeatureFlagEnabled` | Returns a boolean indicating whether the feature flag is enabled. This sends a `$feature_flag_called` event. | | `useFeatureFlagVariantKey` | Returns the variant key of the feature flag. This sends a `$feature_flag_called` event. | | `useActiveFeatureFlags` | Returns an array of active feature flags. This does *not* send a `$feature_flag_called` event. | | `useFeatureFlagPayload` | Returns the payload of the feature flag. This does *not* send a `$feature_flag_called` event. Always use this with `useFeatureFlagEnabled` or `useFeatureFlagVariantKey`. | #### Example 1: Using a boolean feature flag ```react import { useFeatureFlagEnabled } from '@posthog/react' function App() { const showWelcomeMessage = useFeatureFlagEnabled('flag-key') const payload = useFeatureFlagPayload('flag-key') return (
{ showWelcomeMessage ? (

Welcome!

Thanks for trying out our feature flags.

) : (

No welcome message

Because the feature flag evaluated to false.

) }
); } export default App; ``` #### Example 2: Using a multivariate feature flag ```react import { useFeatureFlagVariantKey } from '@posthog/react' function App() { const variantKey = useFeatureFlagVariantKey('show-welcome-message') let welcomeMessage = '' if (variantKey === 'variant-a') { welcomeMessage = 'Welcome to the Alpha!' } else if (variantKey === 'variant-b') { welcomeMessage = 'Welcome to the Beta!' } return (
{ welcomeMessage ? (

{welcomeMessage}

Thanks for trying out our feature flags.

) : (

No welcome message

Because the feature flag evaluated to false.

) }
); } export default App; ``` #### Example 3: Using a flag payload The `useFeatureFlagPayload` hook does *not* send a [`$feature_flag_called`](https://posthog.com/docs/experiments/new-experimentation-engine#experiment-exposure) event, which is required for the experiment to be tracked. To ensure the exposure event is sent, you should **always** use the `useFeatureFlagPayload` hook with either the `useFeatureFlagEnabled` or `useFeatureFlagVariantKey` hook. ```react import { useFeatureFlagPayload } from '@posthog/react' function App() { const variant = useFeatureFlagEnabled('show-welcome-message') const payload = useFeatureFlagPayload('show-welcome-message') return ( <> { variant ? (

{payload?.welcomeTitle}

{payload?.welcomeMessage}

) :

No custom welcome message

Because the feature flag evaluated to false.

} ) } ``` ### Method 2: Using the PostHogFeature component The `PostHogFeature` component simplifies code by handling feature flag related logic. It also automatically captures metrics, like how many times a user interacts with this feature. > **Note:** You still need the [`PostHogProvider`](/docs/libraries/react#installation) at the top level for this to work. Here is an example: ```react import { PostHogFeature } from '@posthog/react' function App() { return (

Hello

Thanks for trying out our feature flags.

) } ``` - The `match` on the component can be either `true`, or the variant key, to match on a specific variant. - If you also want to show a default message, you can pass these in the `fallback` attribute. If you wish to customise logic around when the component is considered visible, you can pass in `visibilityObserverOptions` to the feature. These take the same options as the [IntersectionObserver API](https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API). By default, we use a threshold of 0.1. #### Payloads If your flag has a payload, you can pass a function to children whose first argument is the payload. For example: ```react import { PostHogFeature } from '@posthog/react' function App() { return ( {(payload) => { return (

{payload.welcomeMessage}

Thanks for trying out our feature flags.

) }}
) } ``` ### Request timeout You can configure the `feature_flag_request_timeout_ms` parameter when initializing your PostHog client to set a flag request timeout. This helps prevent your code from being blocked in the case when PostHog's servers are too slow to respond. By default, this is set at 3 seconds. ```js posthog.init('', { api_host: '', defaults: '' feature_flag_request_timeout_ms: 3000 // Time in milliseconds. Default is 3000 (3 seconds). } ) ``` ### Error handling When using the PostHog SDK, it's important to handle potential errors that may occur during feature flag operations. Here's an example of how to wrap PostHog SDK methods in an error handler: ```js function handleFeatureFlag(client, flagKey, distinctId) { try { const isEnabled = client.isFeatureEnabled(flagKey, distinctId); console.log(`Feature flag '${flagKey}' for user '${distinctId}' is ${isEnabled ? 'enabled' : 'disabled'}`); return isEnabled; } catch (error) { console.error(`Error fetching feature flag '${flagKey}': ${error.message}`); // Optionally, you can return a default value or throw the error // return false; // Default to disabled throw error; } } // Usage example try { const flagEnabled = handleFeatureFlag(client, 'new-feature', 'user-123'); if (flagEnabled) { // Implement new feature logic } else { // Implement old feature logic } } catch (error) { // Handle the error at a higher level console.error('Feature flag check failed, using default behavior'); // Implement fallback logic } ```