Each form type has its own Settings section for how (and how often) the widget shows itself. The settings are grouped by what they decide:
A setting's own options appear under its switch only while it's on.
Off by default. Turn it on and the survey opens with a screen of its own before the first question: a title, a short message and a start button. Its three texts are edited in Form copy and are required, in every locale, only while the screen is on. If the survey also lets visitors select an element, the welcome screen comes first and the "what kind of feedback" choice second.
Two ways to lay the survey out, set by Steps display:
Picking One field per screen merges all of the survey's steps into one: Steps then shows a single list of fields with no step tabs, and each field becomes its own screen. Switching back to the default doesn't split them again — the survey keeps that one step.
Picking "one field per screen" adds two more controls:
Either way the indicator has one entry per field, not per step, and a visitor can click any entry they've already passed to jump back to it.
Off by default. Turn it on and the survey shows a language picker in its header, and the visitor can change language while answering without losing what they have already filled in. Choose how it looks under Language picker style: full language names, short codes, or a globe icon.
Covered in full under Languages.
On-site surveys only. Turn it on and the survey shows an expand button in its header; tapping it fills the whole screen. Tapping again returns it to normal size. The same header also gets a close (×) button.
This is aimed at a survey running on a tablet or a kiosk in a physical space — a full-screen form with nothing else on screen is harder to tap out of by accident, and the close button gives staff a deliberate way out.
While it's on, Close redirect URL appears under it: where a visitor goes when they tap the close
(×) button. Leave it blank and they're sent to feedback.voxtrics.io. For a kiosk you'd normally point
this back at your own site, or at whatever page the device should sit on between visitors.
On-site surveys only. Off by default. Turn it on and the survey shows a small sun/moon button in its header that flips it between your light and dark palettes.
Visitors still land on whichever appearance you configured in Attributes — this only lets them change it for themselves, for that visit. Nothing is remembered: the next person to open the link starts from your default again, which is what you want on a shared device.
Off by default. Turn it on and, before answering, the visitor first chooses between pointing at one specific part of the page and giving feedback on the whole page. Choosing "a specific part" switches the page into a hover-and-click picker — the visitor hovers over real page content until the part they mean is outlined, then clicks it. That marks the element for this response: the admin then shows it as its own cropped image on the response, fully styled, in addition to highlighting it on the regular full-page snapshot. The outline color is set in Attributes.
Not available for on-site surveys — the switch is hidden there, since an on-site survey opens on its own page rather than embedded on the page a visitor would actually point at.
Off by default. Turn it on and a visitor who already submitted this survey won't be asked again on a later visit — enforced by matching both their session and IP address against a prior submission (not either one alone), so it can't be bypassed by just clearing a cookie. Requiring both also means two different people submitting from the same shared IP (e.g. coworkers on the same office network) are never blocked by each other — only the exact same session, from the exact same IP, counts as a repeat. Leave it off and the same visitor can submit as many times as they want.
Inline and popup surveys only — an on-site survey is reached by a direct link rather than embedded in a page, so there's no page moment to trigger from and the whole group is hidden there. Every trigger is off by default.
Turn this on and set a number of seconds; the form (or the popup's trigger button) only appears after that delay, counted from page load.
Turn this on and provide a CSS selector — clicking any element matching that selector opens the popup. Useful for wiring a survey to an existing "Give feedback" link or button already on your page instead of relying on delay-based or button-based triggering.
Pick a Status: Returning visitor shows the form only to someone who's been to the site before, and Visitor is leaving is exit-intent — triggered when the cursor moves up and off the top of the browser window, toward the tab bar. Exit-intent only works on desktop: there's no cursor to leave the page through on a touch screen, so a form waiting on this trigger alone never appears on mobile.
Fires once the visitor reaches (or starts at, on a page shorter than the viewport) the bottom of the page.
Set a number N and roughly one in every N visitors sees the form — a random per-visit chance decided in the visitor's browser, not an exact running counter. Use this to sample feedback from a fraction of your traffic instead of showing the survey to everyone.
Provide a cookie name and, optionally, a value. Leave the value empty to match on the cookie's
presence alone; fill it in to require an exact match. The form won't appear if the cookie is
HttpOnly — browsers block scripts from reading those on purpose, so there's no way around this from
the widget's side.
Turn on more than one trigger and the form waits for all of them, not just the first one to fire — a delay plus a click trigger means both have to happen before it shows. A warning at the top of When it appears says so the moment two or more are on, since it's easy to turn on a second trigger without meaning to change how the first one behaves:
The warning doesn't block saving or publishing — it's a heads-up, not a validation error.