You qualify. You're the right age, the right demographic, you buy the product category. You answer three questions — and get screened out. Again. Every survey, same story.

When screen-outs happen that consistently, it's usually not your answers. It's your signals contradicting your answers. The survey's routing engine runs a match check before it even looks at what you said, and your IP is testifying against you.

The match check nobody tells you about

Survey routing works like this: a brand wants "women, 25–40, Chicago area, buys organic snacks." The router doesn't just trust your profile — it cross-checks the technical signals arriving with your session:

  • IP geolocation: where does your IP say you are? City-level, not just country.
  • Browser timezone: does it match the IP's city? A Chicago IP with a Kolkata timezone is a contradiction.
  • Locale and language: en-US vs en-IN, date formats, currency hints.
  • Stated demographics: what your profile claims.

When these four tell the same story, you flow through. When they disagree, the router's safest move is to screen you out — a mismatched respondent is either fraud or bad data, and both are worthless to the buyer.

The five most common mismatches

1. The VPN problem. IP says Dallas, timezone says your real location, profile says a third place. Three stories, zero trust. (Full VPN breakdown here.)

2. Travel without updating. You're visiting family in another state but your profile still says home. Legitimate — but the router can't tell legitimate from fraud, so it screens.

3. Wrong timezone in the browser. Common with misconfigured systems and some privacy tools that spoof timezone. The IP says one city, the browser says another.

4. Carrier-grade NAT on mobile. Your carrier routes you through an IP registered two states away. Nothing you did wrong — but the mismatch is real.

5. Stale profile demographics. You moved a year ago and never updated the panel. Your answers say the new city; your profile says the old one.

City-level targeting: matching on purpose

For people who genuinely operate across regions — or whose connection gives them the wrong city — the fix is making every signal agree. That's what city-level proxy targeting does: you pick an exit IP in the actual city your profile claims, set the browser timezone and locale to match, and suddenly all four signals tell one coherent story.

This is standard practice, not a hack. Market researchers themselves use geo-matched setups when they need respondents from specific cities — the technique is explained in the geo-targeting guide. The key discipline: pick one city per profile and keep it stable. A profile that "lives" in Austin on Monday and Seattle on Wednesday looks compromised.

The consistency checklist

Run through this once per profile and most mystery screen-outs disappear:

  • IP city confirmed on a geolocation checker — does it match your profile city?
  • Browser timezone matches the IP city (not your physical location, the profile's location).
  • Locale matches: en-US for a US profile, not en-IN or en-GB.
  • Profile demographics current: city, age band, household — updated everywhere, identical everywhere.
  • No VPN, no location-spoofing extensions running in the survey profile.

One more thing people miss: answer consistency over time. Panels re-ask demographic questions months apart and compare. If your household size changes between surveys, that's a mismatch too — and it feeds the trust score that governs how many surveys you get offered at all.

When it's not a mismatch

Honest caveat: sometimes you get screened out because the quota filled while you were answering, or the study genuinely doesn't need you. That's normal survey life — even perfect profiles get screened out 20–30% of the time. Quotas fill fastest on popular demographics and high-paying studies, so the surveys you most want are also the ones most likely to screen you late. The problem is only a problem when it's every survey. If it's every survey, it's the mismatch. Fix the signals first.

One more check: your panel profile itself

Before blaming the router, open your panel profile and read it like a stranger would. Is the city current? Does the employment status match what you tell surveys? Are there half-finished profile sections the panel uses for routing? An incomplete profiler is a quiet screen-out machine — the router can't match you to studies it doesn't know you qualify for. Thirty focused minutes updating every section often does more than any proxy change.

Quick poll: when you get screened out, is it usually in the first 3 questions (signal mismatch) or halfway through (quota/quality)? The timing tells you which problem you have.