Archive
Try switching between different user types to see how the same page transforms:
How It Works
You can define different bits of possible data about your users called “claims”. These can include things like whether your user is signed in, whether they're a new customer, or where they're located.
These data can be passed into GitBook via cookies embedded in your app, from your authentication platform, through a feature flagging tool like LaunchDarkly or Bucket, or by passing them in URL parameters.
GitBook checks user data like visitor.claims.isBetaUser == true or visitor.claims.version to show relevant content. This lets you set your docs site so that
API keys auto-fill for authenticated users
Beta features appear only for testers
Enterprise docs show for enterprise accounts
New user guides hide once you're experienced
Why Teams Love Adaptive Content
Faster user success — Users see only what they need, reducing confusion and support tickets.
Higher conversions — Contextual content guides users to the right features for their situation.
One source of truth — Maintain single docs that serve multiple audiences automatically.
See Adaptive Content in Action
This docs site contains different examples of adaptive content.
In the first example, you can click to see how you can tailor your docs homepage to different user types, such as a developer looking for a hands-on getting started guide and a less technical decision maker trying to understand the value of the product.
Ready to Get Started?
Enable adaptive content in GitBook settings
Define user conditions (account type, features, etc.)
Set up data passing (cookies, auth, or URLs)
Create conditional content with GitBook's editor
Test and launch your personalized docs
Experience It Yourself
This demo site showcases adaptive content in action. Try switching between different user profiles using the demo controls to see how the same documentation can serve completely different audiences with perfectly tailored experiences.
Ready to revolutionize your own documentation? Get started with GitBook's Adaptive Content →
Last updated