Create a project per site: list the domains allowed to submit, and bind the integration its reports should reach. Each site gets its own rules β no cross-talk.
Everything else inherits from these four settings.
A container for one site or product, with its own key, reports and retention.
Only the domains you list can submit reports through the Web SDK key.
Which integration receives this project's reports by default.
A project belongs either to you or to a team, and inherits that visibility.
The Web SDK key is visible in your page source. The whitelist is what makes that safe.
| Matching | Exact host and wildcard subdomains |
|---|---|
| Unlisted domains | Submissions are rejected server side |
| Local development | Add localhost with a port to test safely |
| Rate limits | Applied per project per day and per IP per day |
acme.com
app.acme.com
*.staging.acme.com
localhost:3000Every project is bound to its own integration: your UAT site reports into the UAT table, your marketing site into its own. The default already lands in the right place, with no manual sorting.
| Where it came from | Default destination |
|---|---|
| Web SDK submission on a whitelisted domain | The project's bound integration |
| Browser extension on a whitelisted domain | The site project, as chosen in the destination dropdown |
| Extension on a domain with no project | The reporter's team or personal destination |
| Manual override by the reporter | Whatever they select, remembered for that site |
One person configures, the whole team shares.
Send reports into Feishu Bitable or any webhook you own.
One script tag lets any site visitor report without installing anything.
During internal validation, testers and stakeholders report into the same project.