On-site survey

An on-site survey isn't embedded on your website at all — it's hosted on its own page on our domain (/s/{surveyId}) and reached by sharing a direct link. There's no script to add to your site for this type; the Embed step in Quick Start doesn't apply here.

Use cases

• Feedback requests sent by email, chat, or SMS.
• Surveys linked from a QR code, a receipt, or anywhere else outside a webpage.
• Gathering feedback from a specific, known list of people rather than anonymous site visitors — e.g. internal questions inside your own company, sent to a known list of employees via Per-recipient links (note: per-recipient links identify who submitted — see the access modes below for what "known list" actually means here).
• A stationary screen in a physical store or shop, open to the survey's link (Open or Shared link access) all day, for customers to leave instant feedback on the spot.

How to access it

Once published, the survey's Access tab shows a ready-to-copy link on our domain (something like https://feedback.oiva.dev/en/s/{surveyId} — not your own site's domain, since there's nothing to embed here), optionally with a ?token=... query parameter depending on the access mode below. Anyone who opens that link sees the hosted form directly — no login required.

Ways to secure it

Three access modes, set on the survey's Access tab — only one is active at a time; switching modes replaces the current setup:

• Open — anyone with the link can view and submit. No token needed.
• Shared link — a single token, the same for every visitor, appended to the link as ?token=.... Anyone without the exact link (including the token) can't reach the form. You can regenerate the token at any time, which invalidates the old link.
• Per-recipient links — a unique, single-use token generated for each recipient (either from a pasted list of labels/emails, or as a batch of anonymous tokens). Each link identifies that specific recipient and is consumed the moment they submit, so it can't be reused — and each one can be individually revoked before it's used. A table on the Access tab tracks every generated link's status (used/unused) with a copy-link and revoke action per row.

Running it on a tablet or kiosk

A few Settings options exist specifically for a survey left open on a device in a physical space — a screen by the till, a tablet at a reception desk:

• Allow full screen gives the survey an expand button and a close (×) button in its header.
• Close redirect URL decides where closing sends the device — usually back to your own site, rather than the default feedback.oiva.dev.
• Let visitors switch light/dark theme adds a sun/moon button so someone can flip the survey to suit the room's lighting without changing your default for everyone else.
• One field per screen (Steps display) shows one question at a time, which reads better at arm's length than a dense multi-field form.

All four are on the survey's Settings tab.

Publishing requirements

Same baseline as every type — at least one step, at least one field, all translations filled. Like inline forms, a missing main-evaluation or main-feedback field is a non-blocking warning here, not a hard error.