
PostHog Flags SDK Example
This example uses PostHog for feature flags with the Flags SDK along with the @flags-sdk/posthog PostHog adapter and the Flags Explorer.
Demo
https://flags-sdk-posthog.vercel.app/
How it works
This demo uses two feature flags in PostHog to control the visibility of two banners on the page. Both gates are configured to show/hide each banner 50% of the time.
If you deploy your own and configure the feature flags in PostHog, you can also use the Flags Explorer to enabled/disabled the features.
Deploy this template
Clicking the button above will:
- Clone this repository to your GitHub account
- Create a new Vercel project
- Install the PostHog integration from the Vercel Marketplace (automatically configures
POSTHOG_PROJECT_API_KEYandPOSTHOG_HOST) - Prompt you to generate a
FLAGS_SECRETfor the Flags Explorer
Step 1: Link the project
In order to use the Flags Explorer, you need to link the project on your local machine.
vercel linkSelect the project from the list you just deployed.
Step 2: Pull all environment variables
This allows the Flags SDK and the Flags Explorer to work correctly, by getting additional metadata.
vercel env pullStep 3: Create Feature Flags
Head over to PostHog and create the feature flags required by this template.
Feature Flags:
Summer Salewith the keysummer_saleFree Shippingwith the keyfree_delivery
You can also find the feature flag keys in the flags.ts file.
Set both feature flags to rollout to 50% of users.
Manual Setup (without Marketplace integration)
If you prefer not to use the Vercel Marketplace integration, you can manually configure the environment variables:
- Set
NEXT_PUBLIC_POSTHOG_KEYto your PostHog project API key - Set
NEXT_PUBLIC_POSTHOG_HOSTto your PostHog host (e.g.,https://us.i.posthog.com) - Set
FLAGS_SECRETto a base64-encoded 32-byte random value
For the Flags Explorer feature, also set:
POSTHOG_PERSONAL_API_KEY- Your PostHog personal API keyPOSTHOG_PROJECT_ID- Your PostHog project ID


