Embedding the Feedback Portal
Embed the Feedback Portal in a page of your product, match its appearance, and keep customer identity and access rules.
Written By Robi Rohumaa
Last updated 41 minutes ago
Overview
The embedded Feedback Portal puts feedback browsing and submission inside your website or web app. Customers can use the portal without opening a separate tab.
Note: Your Feedback Portal must be enabled before you install the embed. Configure its categories, participation rules, and portal settings first.
Embed the Feedback Portal
1. Choose what to embed
Use the feedback page as the starting view when customers need to browse, search, vote, and submit Requests. The embed also supports other portal views, such as an embedded Roadmap, so choose the starting page for the job customers are doing.
You do not need to create a second set of Requests or categories for the embedded view.
2. Install the embedded portal
A developer needs to add the embed to your product. For a native mobile app, use the mobile app embed guide instead.
Open the portal embedding instructions
Add the SDK and the embed container to the page where feedback should appear
Configure your Workspace, the starting page, and the container's layout
Open the page in your product and check that the portal loads; a site with a Content Security Policy must allow Featurebase first
Tip: Choose a container size that leaves enough room to browse Requests and use the submission form.
3. Match appearance and language
Set the embed's theme and language to match the surrounding page. Keep the Feedback Portal wording and Customer Portal appearance consistent with your product.
You can hide the embedded portal's menu or logo when your product already provides that navigation and branding.
4. Identify customers and preserve access
Identify customers with identity verification so they use their product identity in the embedded portal instead of creating a separate one. The embedded portal still applies your portal access and category access rules.
5. Test the embedded portal
Test from a customer session in your product:
Open a Request and return to the feedback list
Submit a Request and check the customer identity in Featurebase
Check a customer who can access restricted content and one who cannot
Confirm the language, theme, and visible navigation
Also test a signed-out session if your product permits one.
Tip: If a customer cannot open content, check their identification and access rules before changing the embed's appearance options.