Answers before
you even ask.

No. The site key is a public identifier that ships with the embed script in your page source; it cannot be used to sign in or manage anything. Reading and triaging feedback requires a console session or an API token. If you worry about someone abusing your site key, configure the allowed origins list below.

It is a submission allowlist: only pages loaded from these origins (scheme + host + port, such as https://example.com) may submit feedback. Leave it empty to allow any origin. Note that https://example.com and https://www.example.com are different origins, and local development needs its own http://localhost:port entry.

Check in order: whether the script is blocked by a CSP, an ad blocker, or a wrong path; whether the browser console shows errors; and, if you use a custom button, whether you set launcher: false and call FeedbackPlus.open() only after the script has loaded.

Yes. Set launcher: false during init, then call FeedbackPlus.open() from any button's click handler. The integration modal and the help center both include copy-ready examples.

Yes. After creating a site, the integration modal offers five copy-ready variants: standard script, WordPress, React, Vue, and GTM. Pick whichever matches your stack.

Yes. Every site has a hosted feedback page (/f/<siteKey>). Share the link in email, chat, or docs and people can submit directly; the feedback lands in your console just the same.

The message, an optional contact from the reporter, the page URL, page title, browser, operating system, device and viewport details, plus an optional page screenshot.

Regions marked with the data-feedback-private attribute are excluded by default, and you can add your own selectors via the exclude option. Mark password fields, payment panels, and profile cards, then submit a test feedback before going live to confirm what the screenshot contains.

Cross-origin images, iframes, video, and canvas may not fully render into DOM screenshots — a known limitation. If screenshots are too heavy or slow on weak networks, switch screenshotMode to balanced or compact.

Add notification channels in the console's message settings. DingTalk, Feishu, Telegram, Discord, Slack, and custom webhooks are supported, and new feedback is pushed per site to the channels you choose.

The console filters and searches feedback by site, status, priority, and category. Each item keeps the reporter's original words and also carries a generated title, category, and priority for triage.

Yes. Install the fbpp CLI or follow the Agent Skill guide; agents can pull feedback, download screenshots, and update status. API tokens are generated in account settings — treat them like passwords and never commit them to a repository.

It is currently free to integrate and use. If paid plans are introduced in the future, they will be announced on the website and in the console in advance.

Your feedback and screenshots belong to you. Deleting a website or a feedback item also deletes its associated screenshot; see the privacy policy for full retention, deletion, and export details.

Yes. Feedback++ ships a local Node runtime (Node 24 or newer); clone the repository and run npm run dev. Production runs on Cloudflare Workers + D1 + R2.

Click your avatar at the bottom left of the console to open account settings: update your name and password (other devices will need to sign in again), or rotate your API token (the old token stops working immediately).