Layer 2 — collect

Ask the person who's leaving right now

Not another NPS widget blasted at every visitor. Polaris surveys are built to reach one specific person, in one specific moment — usually the one about to bounce.

Targeting

9 rules to reach exactly the right visitor

UTM parameters

Target visitors from a specific campaign or source.

Device

Mobile, tablet, or desktop only.

Country

Geo-target by visitor location.

Browser

Isolate a browser-specific issue you suspect.

URL pattern

Fire only on the checkout page, or anywhere but it.

Custom JS condition

Anything your own logic can express — cart value, logged-in state, whatever you track.

OS

iOS vs Android vs desktop OS-specific targeting.

Delay

Wait N seconds on page before it's eligible to show.

Exit intent

Fire the moment a cursor heads for the tab bar or back button.

Branching

Every answer leads somewhere

A "no" answer branches to a different follow-up than a "yes." The result in your report isn't a flat list of responses — it's a tree, so you can see exactly where an answer path led and how often.

Q1 — "What's stopping you from checking out today?"
"Price" → 38%
↳ follow-up: which plan?
"Just browsing" → 44%
↳ follow-up: remind later?
"Missing info" → 18%
↳ follow-up: which info?
Not NPS

The thesis

A quarterly NPS blast tells you how people feel in general. It doesn't tell you why the visitor on the pricing page right now, three seconds from leaving, is about to leave. Polaris surveys are built for the second question, because that's the one connected to a number you can move this month.

"How likely are you to recommend us?" — asked to everyone, quarterly
"What's stopping you right now?" — asked to the visitor leaving the checkout page, this second
Get started

See what a first audit surfaces

Surveys ship after the one-tag snippet — the first report doesn't need it.

Get a free audit of your site