One widget per project: when and why
Buganalyst
You can create as many widgets as your plan allows—and for most teams, one widget per project is the sweet spot.
Clear ownership
Each widget has its own embed code, Slack webhook (or channel), and Trello board/list. That means reports from your marketing site don't mix with reports from your main app, and each team can own their pipeline.
Easier triage
When a report arrives in Slack or Trello, the source is obvious. You're not guessing whether the bug is on the blog or the dashboard.
Flexible scaling
Free tier gives you one widget; Pro and Team add more. Start with one for your primary product, then add widgets for landing pages, docs, or client projects as you grow.