Installation overview

Learn how to install Featurebase on your website with this quick 101 guide.

Written By Bruno from Featurebase

Last updated 3 days ago

Overview

Featurebase ships as a single JavaScript SDK that you install once at your app root. Once installed, every Featurebase surface β€” Messenger, the Feedback widget, the Changelog widget, Surveys, and the embedded web portal β€” picks up your appId and the signed-in user automatically. Setup typically takes a few minutes of engineering time.

πŸ‘¨β€πŸ’» Feel free to share this guide with your engineer or a technical team member who can assist.


What you'll need


1. Install featurebase-js

Install the package from npm β€” or, if you can't run a build step, drop the legacy script tag into your <head>.

Example
npm install featurebase-js

2. Boot the SDK once at your app root

This single call is what gives every widget its identity and appId. Pick whichever tab matches your stack β€” the result is the same.

Example
// app/layout.tsx β€” Next.js 13+, or any React root. 'use client'; import { FeaturebaseProvider } from 'featurebase-js/react'; export default function RootLayout({ children, user }) { return ( <FeaturebaseProvider appId="YOUR_APP_ID" // Settings β†’ Developers β†’ Installation // featurebaseJwt={user?.featurebaseJwt} // recommended for logged-in users > {children} </FeaturebaseProvider> ); }

For logged-in users, generate a JWT on your server and pass it as featurebaseJwt. For anonymous visitors you can leave it out β€” Messenger will treat them as leads.


Identify your users (recommended)

For logged-in apps, identify users with a server-signed featurebaseJwt. This is the production-safe path and works with secure installation enabled by default.

πŸ‘‰ Full guide: Identifying users & syncing data.


3. Mount the widgets you need

Messenger boots automatically from the universal install above as long as it's enabled in your dashboard. Every other widget needs one extra mount call β€” pick a page below for the per-widget guide:


Public portal SSO

If you want users to access your public Featurebase portal through your own identity provider, set up Single Sign-On. This is separate from the SDK boot above: the SDK identifies users inside your product, while SSO controls direct login to the hosted public portal.

πŸ‘‰ Web portal SSO setup β€” authenticate users to the public portal with your own IdP.


Advanced

For API, metadata, and other advanced setups:


Have any questions?

Please feel free to message us via live chat or at support@featurebase.app. We'll get back to you as soon as we can, typically within a few hours. πŸ™ Thank you!