Forcing Users to Sign Up Is Killing Your Feedback Board

Requiring account creation before feedback submission cuts response rates by roughly 70%, based on widget install data from 2,800 Feedbask customers who A/B tested gated vs anonymous flows over the past year. One indie founder on Indie Hackers put it plainly while shopping for alternatives: they wanted a tool that "doesn't require users to create a new account like Canny so users actually use it." That's not a niche opinion. That's the market.

TL;DR:

• Every extra field before submission drops completion by 10 to 15% (Baymard-style checkout research applies to feedback too).
• Anonymous-first with optional email capture outperforms account-required by 3 to 5x on raw submissions.
• Spam is solvable without sign-up walls. Rate limiting, honeypots, and content heuristics do the job.

The Cost of the Signup Wall

Every account creation screen is a tollbooth between you and the data you need.

A user who just hit a bug or had a genuinely good idea is operating on impulse. They have maybe 90 seconds of motivation. If the first thing they see is a sign-up form, the bug stays in their head, the idea stays in their head, and your roadmap stays wrong.

The math is ugly. Baymard Institute's long-running ecommerce research pegs account creation as the single biggest cause of checkout abandonment, above shipping cost and above slow load times. The same psychology applies to feedback forms. If anything, it's worse, because the user is doing you a favor, not buying something they want.

We pulled anonymized funnel data from widgets that offered both flows. Median conversion from "widget opened" to "feedback submitted":

The jump from "optional email" to "no email at all" is smaller than you'd think, which matters because optional email is the sweet spot for follow-up without killing volume.

Why Canny's Default Kills Submissions

Canny is a good product. Its default configuration is the problem.

By default, Canny asks users to create an account or log in with SSO before they can post or upvote. For internal employee feedback tools that's fine, there's already a corporate SSO in place. For customer-facing feedback boards on an indie SaaS, it's a leak in the funnel.

The tradeoff Canny's default optimizes for is identity. Knowing who filed each piece of feedback is genuinely useful for enterprise customer success teams. For a bootstrapped SaaS with 400 monthly active users, having five identified submissions is worse than having fifty anonymous ones. You can email the anonymous submitters for details. You can't email the people who bounced off your sign-up wall.

The same applies to any feedback tool that treats identity as a prerequisite instead of an enrichment. ProductBoard, Pendo's feedback module, and older Jira Service Management flows all make the same mistake by default. Flip the setting if you can find it.

The Anonymous-First Pattern

Open the form. Let them type. Ask for email in a second field that doesn't block submit.

The pattern looks like this:

1. User clicks "Send feedback" or hits your widget.
2. Widget opens to a single textarea: "What's on your mind?"
3. Below the textarea: optional title, optional email, optional category.
4. Big submit button.
5. After submit: thank-you screen with an optional "Want an update when we fix this?" email capture as a secondary CTA.

That second email ask after submission is the highest-converting one. Users who just finished writing a paragraph are already invested. Asking then is a smaller request than asking upfront.

Feedbask's widget ships with this flow as the default. You don't have to configure anything. If you want to see how it looks in the wild, browse any widget demo on /product/website-feedback-widget and open the embed without logging in.

Preventing Spam Without Accounts

The argument for sign-up walls is always spam. It's a bad argument.

Spam on feedback forms is solvable with four layers that don't cost the user anything:

1. Rate limiting by IP and session: one submission per minute per IP is enough to stop the vast majority of bot traffic. Five per hour stops the rest.
2. Honeypot fields: a hidden input named "website" or "company_phone" that real users never fill but bots always do. Drop anything with that field populated.
3. Content heuristics: reject submissions shorter than 8 characters, longer than 20,000, or containing more than three URLs. Tune per your audience.
4. Optional Turnstile or hCaptcha: invisible by default, only challenges suspicious sessions. Users never see it unless they look like bots.

Across Feedbask widgets with these four layers enabled and no account requirement, spam rate sits around 0.3% of total submissions. That's lower than the spam rate on most authenticated forums, because spammers specifically target authenticated boards to build reputation.

Progressive Profiling for the Users Who Matter

Anonymous doesn't mean unknowable. It means you collect identity piece by piece.

The progressive profiling model works like this. First submission is anonymous. If the user includes an email, you attach that to their browser session. Second submission from the same browser auto-fills the email. Third submission can offer to create a lightweight account for notifications and upvote tracking. By the time you ask for a password, the user has already gotten three wins from your product and has a reason to say yes.

Feedbask's backend does this automatically via a browser-level identifier cookie. You see merged threads in your dashboard even when submissions came in anonymously across weeks. The user sees a friction-free experience.

The key insight: only 10 to 15% of feedback submitters ever become power users of your public board. The rest drop feedback once and leave. You don't need accounts for the 85% who drop off, and the 15% who engage will happily sign up once they're hooked.

Embed Patterns That Work

Four embed patterns convert better than the default "button in the corner".

First, inline forms on relevant pages. A feedback textarea at the bottom of your pricing page, your docs, or your error pages catches users at moments of active reflection. Install with a single div:

<div data-feedbask-inline="pricing-feedback"></div>
<script src="https://cdn.feedbask.com/widget.js" defer></script>

Second, post-action triggers. After a user exports a report, publishes a post, or completes onboarding, pop a small "How did that go?" prompt. Conversion on these is 3 to 4x a generic sidebar button.

Third, in-app contextual widgets. For logged-in users, pre-fill the email field from their session but keep it editable and optional. See /product/in-app-feedback-widget for the patterns that work best inside a signed-in product.

Fourth, public board with one-click upvoting. No login required to upvote. Track by browser fingerprint or IP, tolerate a little duplicate voting, accept that signal matters more than precision. Configure this under your feature voting setup at /product/feature-voting-tool.

Combine two or three of these and you'll see submission volume multiply within a week.

FAQ

Doesn't anonymous feedback produce lower quality submissions?

Slightly, but you get 5x more of them. Sorting through more feedback is a better problem than not having any. The signal-to-noise ratio on anonymous submissions is around 70% useful in our data, versus 85% on authenticated boards. You are trading a 15% quality drop for a 5x volume increase.

How do I follow up on anonymous bugs without an email?

Make email optional, not required. About 55 to 65% of anonymous submitters will voluntarily leave an email if you ask nicely and explain why. That's still more identified users than a sign-up wall produces.

What about impersonation or abusive submissions?

Rate limiting handles volume-based abuse. For targeted harassment, offer a moderation dashboard that lets you hide or delete submissions and ban IPs. Feedbask includes both by default.

Should upvotes require accounts?

No. Track upvotes by browser plus IP. Yes, someone can vote twice from two browsers. That's fine. You're looking for relative signal, not precise counts.

Do enterprise customers actually want anonymous feedback?

Enterprise buyers typically want SSO-gated boards for their internal employee feedback. That's a separate product mode, not your default. Ship both, toggle by team plan.

What's the one setting I should change today?

If you're on Canny, ProductBoard, or a similar tool, go into settings and turn off the "require sign-in to post" toggle. Watch submission volume over the next week. If it doesn't at least double, then your user base genuinely prefers accounts, which is rare.

If your current feedback tool is forcing account creation and you're getting crickets, that's the tool, not your users. Try Feedbask free and ship with anonymous-first as the default.