Teardowns and before/after case studies·

The "How Did You Hear About Us?" Field Is a Signup Leak: A Mini Playbook to Fix It

The "How Did You Hear About Us?" Field Is a Signup Leak: A Mini Playbook to Fix It

You've got real traffic. Your pricing is fine. Your product is fine. But your signup form has one field that's quietly telling users: "Do me a favor before I do anything for you."

That field is "How did you hear about us?" — and it's easier to fix than you think. Let's tear it down.

Why a Single Field Can Sink Your Signup Step

When a user lands on your signup step, their mental model is "I want to get in." The "How did you hear about us?" dropdown does the opposite: it switches the conversation from the user's goal to your marketing attribution. It asks an unpaid question before the user has gotten any value.

Three things happen:

  • Cognitive load. A dropdown with 6+ options is a decision. The user has to stop and think about where they found you, which is irrelevant to getting started.
  • Trust erosion. "Why do you need this?" feels like surveillance. It triggers a common Nielsen-style heuristic: the system should speak the user's language, not the marketing team's.
  • Friction. In a signup flow, every second of hesitation costs you a signup. This field is pure hesitation.

Not to mention it's a hierarchy problem. The field is given the same visual weight as "Password" — and it's not even a user goal. If you're tracking drop-off, this is one of the easiest leaks to fix.

The Before: A Form That Asks for a Favor

Here's what most SaaS signup forms look like:

Email address
[________________]

Password
[________________]

How did you hear about us?  (required)
[ Select one                v ]

[ Create Account ]

See the problem? The user just wants a trial, not a survey. The field is required, fully expanded, and gets the same visual weight as the password field. If you're losing people at this exact point, you now know why.

The After: Move Attribution Out of the Conversion Path

You don't have to delete the data — you have to move it. Here's the rewrite:

  • Before: "How did you hear about us?" (required)
  • After (Option A): Delete the field entirely. Email + Password + "Start my trial."
  • After (Option B): Move it to a one-question survey after the user activates their workspace. Make it optional and include a "Skip" link.

A collapsed optional version doesn't work as well as moving it entirely — because the field still creates a moment of doubt. Users will wonder if they're missing something.

The Mini Playbook: Fix This Step in One Afternoon

  1. Confirm it's the leak. Don't guess. Run a free audit on your signup flow and watch two or three session recordings where users hit this field. You'll see the hesitation.
  2. Make it optional, then move it. If removing is a political battle, make it optional and collapsed. Then in the next sprint, move it to an in-app survey after the user's first "aha" moment.
  3. Rewrite the label if you keep it. Change "How did you hear about us?" to "What brought you here today?" and make it optional. It's friendlier, but still a question. Best used only as a temporary measure.
  4. Track the change. Compare activation rate before and after. You don't need a full experiment — a simple before/after over two weeks will show you the impact of removing one field.

P0 / P1 / P2 Breakdown

  • P0: Remove the required "How did you hear about us?" field from the signup step. This is the highest-impact fix. If legal requires it (rare), make it optional and collapsed.
  • P1: Move the attribution question to an in-app survey after the user gets value — e.g., after their first project is created or first report is generated. Include a "Skip" link.
  • P2: Rewrite the survey question to be about benefit, not marketing. "What made you decide to try FlowAudit?" beats "Where did you come from?" every time.

Your Turn

Now go look at your own signup form. Is there a field that's only serving you and not your user? If you want a second pair of eyes, start a free FlowAudit at /signup and get a prioritized P0/P1/P2 fix list for your flow — including the exact field to remove first.