Stedica Surveys & Forms

By Stedica

0+ active installationsVersion 5.53.1

Surveys, forms and quizzes: drag-and-drop builder, logic, scoring, entries, offline collection and AI with your own key. No limits.

Description

Stedica Surveys & Forms builds surveys, forms, quizzes and lead-generation
funnels on your own WordPress site. Drag questions into sections, add logic and scoring, show
a result screen that fits each answer, and publish with a block, a shortcode,
a popup, a link or a QR code. Responses stay in your own database.

Why people choose it:

  • No limits. Unlimited surveys, questions and responses. Nothing is
    time-limited, capped or switched off pending a purchase.
  • Forms as well as surveys. Contact, order and booking forms with an
    Entries inbox, email notifications, spam protection and a built-in link to
    Stedica CRM.
  • Quizzes and funnels in the free plugin. One question per screen, a start
    screen, quiz scoring and result screens chosen by answers or score.
  • Know what works. A funnel report (views, starts, completions) per
    traffic source, drop-off by question, and events for GA4, Google Tag Manager
    and the Meta pixel.
  • Works with no signal. Offline collection for field work, store visits
    and events; answers sync when the connection returns.
  • AI on your terms. Write a survey or quiz from a description with your
    own Anthropic, OpenAI, Gemini or self-hosted key. AI assistants such as
    Claude and ChatGPT can read your results over MCP, and can change or delete
    anything only if you switch that on. Off until you connect one; nothing
    passes through us.
  • Accessible. Built to WCAG 2.2 level AA, with a published statement.

Everything listed below works in this plugin.

Forms

  • Make a survey or a form: a form shows all fields on one page, with form
    labels and its own templates (contact, contact or consultation, quote
    request, call-back, event registration, newsletter sign-up).
  • Form fields: name, email, phone, website, address, consent, hidden field,
    text block, page break, date and time; fields side by side in columns.
  • Checks on the server as well as in the browser, a confirmation message or
    redirect after sending, and Calculated Fields worked out on the server.
  • Entries inbox: statuses, search, notes, edit, resend notifications and
    print.
  • Two team notifications per form, with Cc and Bcc, plus a confirmation to
    the person who sent it.
  • Spam folder, blocklist, Akismet, and an optional CAPTCHA (off by default).
  • Send entries to Stedica CRM with field mapping, and accept entries over a
    REST endpoint.

Building

  • Drag-and-drop builder — reorder sections and questions by dragging
  • Unlimited surveys, unlimited questions per survey
  • 17 question types — surveyor, open ended, closed ended, multiple choice,
    Likert scale, dichotomous (yes/no), rating, number, dropdown, matrix,
    ranking, image choice, demographic, calculated field, photo upload, date,
    signature
  • Select all that apply — a multiple choice question can take several
    answers, with an optional limit and a “None of the above” that clears the
    others
  • Conditional logic — show or hide questions based on earlier answers
  • Answer piping — put an earlier answer into a later question’s wording:
    “How was your visit to {answer:q1}?”
  • Option randomisation — shuffle a question’s answer options per respondent
    to cancel order bias, with “Other” and “None of the above” pinned in place

  • Popups, slide-ins and launcher buttons — open a survey after a delay,
    a scroll depth or on exit intent, with page targeting and frequency limits

  • Survey links, QR codes and embeds — share any survey by its own
    address, a printable QR code or an iframe, without building a page
  • 29 starter templates by industry — lead quizzes and scorecards,
    customer experience (NPS, CSAT, CES, post-purchase, restaurant, patient),
    HR, market research, field inspections, education and community
  • Write it with AI, with your own key — describe a survey or quiz, or give
    the address of a page, and get a draft with questions, scoring and result
    screens to check before anything is created; draft result texts in the
    Builder. Works with Anthropic (Claude), OpenAI, Google Gemini, your own
    OpenAI-compatible server, or on WordPress 7.0+ the AI connection set once in
    Settings → Connectors, and is off until an administrator connects one
  • Import an XLSForm — bring a form from ODK, KoboToolbox, SurveyCTO or
    Ona, with its sections, choices, show rules and piping, after a preview
  • Import a paper or PDF form with AI — upload a PDF or photos of the pages
    and get the same questions, options and skip rules as a survey to check,
    using your own AI key
  • Works with AI assistants (MCP) — on WordPress 6.9+, Claude, ChatGPT,
    Cursor and other assistants connected through the MCP Adapter can read your
    surveys, results, responses, written answers and drop-off, and, only if you
    allow it, create, copy, rename, share or delete them, as a user you choose
  • Step mode, start screen, quiz scoring and result screens — one question
    per screen with Back and Next; options carry points; result screens are
    chosen by answer rules or score range, and the outcome and score are saved
    with each response, in exports, emails and webhooks
  • Fill from URL parameter — start a question with a value from the page
    address, such as a store number (?store=1042)
  • Question Library — save a question once, reuse it across surveys
  • Survey versioning, with a Go-Live mode that locks schema changes

Keeping responses trustworthy

  • Spam protection — a hidden decoy field, a submission-timing check and a
    per-connection rate limit. No CAPTCHA, nothing sent to any third party, and
    nothing for the respondent to do
  • One response per person — by WordPress account, by browser, or by network
    address, with the limits of each stated where you choose it
  • Response cap — close the survey automatically once it reaches a set number
  • Anonymous responses — do not record which account submitted a response
  • Response quality flags — responses finished far faster than the survey’s
    median, with every scale answered the same, with questions answered too fast
    to read, or with exactly the same answers as another response, are flagged
    for review, with the evidence
  • Real times for offline responses — a response collected with no signal
    is timed by the device, not by when it synced
  • How each response was answered — optional per survey: seconds on each
    question and the kind of device, stored with the response

Collecting

  • Shortcode [stedica_survey id="123"], a Gutenberg block, an
    Elementor widget, a Bricks element and a Divi module
  • Offline capture, switchable per survey — a progressive web app queues
    answers on the respondent’s device with no connection and syncs them when the
    signal returns. Turn it off per survey for anything only ever taken online
  • Offline Sync Monitor showing what is queued and what has landed
  • Progress bar, and save-and-resume for long surveys
  • Photo upload for image evidence, with server-side validation

Notifying

  • Email notification when a response is submitted, to any list of recipients
  • Confirmation email back to the respondent, when the response contains an
    address
  • Merge tags for the survey name, the respondent, any individual answer, or the
    whole response
  • Set defaults once for every survey, then override them per survey
  • Optional Reply-To the respondent, so replying reaches the person
  • Responses collected offline notify when they sync, not silently
  • Webhooks — POST each response to a URL you enter, so another system can
    react to it. Automatic retry if the endpoint is down, and a Send test button
    so you can prove it works before going live

Reading

  • Results dashboard — response counts, completion rate, per-question breakdowns,
    section metrics and a submission timeline
  • Charts — doughnut, bar, stacked bar and a response-over-time line, chosen
    automatically to suit each question type. Every chart carries a matching data
    table, so the figures are readable by screen readers and copyable
  • Net Promoter Score — promoters, passives and detractors, with the score
    and the base
  • Cross-tabulation — break one question down by another (satisfaction by
    region), with row, column or total percentages
  • Individual response viewer — open one response and read it as a document,
    every question in order, with the wording that was on screen when it was
    answered
  • Funnel and sources — views, starts and completions with rates, overall
    and per source (UTM tags, else the referrer); UTM tags and chosen URL
    parameters are saved with each response
  • Analytics events — survey view, start, completion and outcome sent to
    Google Tag Manager, GA4 or the Meta pixel, after consent through the WP
    Consent API
  • Drop-off analysis — how far respondents get and where they stop
  • Question drill-down
  • CSV and Excel (XLSX) export of every response
  • REST API for external reporting tools
  • Per-survey backup, restore, and clear-data

Running it safely

  • A Survey Editor role, so people can build surveys without full admin rights
  • Admin audit log
  • GDPR personal-data exporter and eraser, wired into WordPress’s own privacy tools
  • Plugin Health screen that checks tables, capabilities and scheduled jobs

Accessibility

Surveys are built to WCAG 2.2 level AA. Every question has a real label,
choices are grouped with their question, required questions say so in text,
and the survey works with a keyboard alone. A missing answer is marked on the
question itself and listed at the top, and focus moves to it. Screen readers
hear when questions appear or no longer apply. Text and buttons meet AA
contrast, controls are at least 24 by 24 pixels, and the survey reflows to a
320-pixel-wide screen. See the FAQ for the full statement and the known
exceptions.

Extensions, sold separately

These are separate products and are not required. This plugin is complete
without them.

  • Stedica Surveys & Forms Premium — for lead funnels, quizzes and field teams:
    • Lead form before the questions or before the result, branding, answer
      cards with images, and WooCommerce product recommendations with revenue
      from paid orders per result
    • Personal PDF result reports, result emails with follow-ups and an
      abandon reminder
    • Quiz tools: answer reveal with explanations, time limit, question pools,
      personality scoring and PDF certificates
    • A/B tests with an automatic winner
    • CRM and app connectors: Mailchimp, HubSpot, ActiveCampaign, Brevo,
      FluentCRM, Klaviyo, Google Sheets and Slack, with retries and alerts
    • Multilingual surveys (WPML, Polylang or built-in) and data retention
    • AI on your own key: insights and next steps from your results, with the
      figures behind each point; a chat that answers questions about them;
      open-text analysis (themes, sentiment, summary); and a follow-up question
      when a written answer is vague
    • Leads, A/B test results and field cases for connected AI assistants
    • Field teams: review states, a field collector role, territories, offline
      case lists, a map shape question, GPS capture, geo and territory
      dashboards, KPI risk alerts, and a live feed for Power BI and Excel
  • Data Sources add-on — question options from an imported CSV or XLSX
    file or from WordPress users, with dependent dropdowns that work offline
  • AI Images add-on — product recognition, image captions and image
    comparison for photo questions, with the AI provider connected here or the
    add-on’s own OpenAI key

External services

Nothing is sent anywhere by default. Out of the box this plugin makes no
outbound requests: surveys, responses and uploads stay in your own WordPress
database and on your own server.

Five things can send data out, and all are off until you switch them on.

Webhooks (optional, off by default)

If you enter a webhook URL under Stedica Surveys & Forms → Notifications, each completed
response is POSTed to that URL — one you choose, not a service we run. The
request contains the survey id and name, the response id and submission time, and
the answers. It does not include IP or device hashes, WordPress user ids, or
internal version ids.

Requests go out through WordPress’s own wp_safe_remote_post(), which refuses
private and reserved network addresses. If you set a signing secret, each request
carries an X-Stedica-Signature header — HMAC-SHA256 of the request body — so
your endpoint can verify it. The secret itself is never transmitted.

Because the destination is yours, its terms and privacy policy are whatever
applies to the endpoint you point it at.

AI writing (optional, off by default)

An administrator can connect an AI provider in Stedica Surveys & Forms → Settings → AI,
with their own API key, or on WordPress 7.0 and later choose the WordPress AI
connection, which uses the provider and key set in Settings → Connectors. Until
then nothing is sent. Once connected, a request
is made only when someone who can edit surveys clicks an AI button: Write the
draft
on Add New, or Write with AI on a result in the Builder.

What is sent: the description typed into the AI box, the chosen kind, number of
questions and language; when a page address is given, the readable text of that
page (fetched by your site with wp_safe_remote_get(), which refuses private
and reserved addresses); and for a result text, the survey’s name, its question
labels and options, and the result’s title, rule and current text. This plugin
never sends responses or respondents’ details. An add-on that uses the same
connection says on its own screen what it sends: the Premium add-on’s
open-text analysis, for example, sends the written answers to the one question
you pick, without names or emails, when you click Analyse answers; the AI
Images add-on, when set to use this connection, sends the respondent’s photo
(and for product recognition the question’s product list) when a photo is
analysed.

It goes straight from your site to the provider the administrator chose, using
their key; nothing passes through Stedica:

  • Anthropic (Claude) — api.anthropic.com.
    Terms: https://www.anthropic.com/legal/commercial-terms —
    Privacy: https://www.anthropic.com/legal/privacy
  • OpenAI — api.openai.com.
    Terms: https://openai.com/policies/terms-of-use/ —
    Privacy: https://openai.com/policies/privacy-policy/
  • Google Gemini — generativelanguage.googleapis.com.
    Terms: https://ai.google.dev/gemini-api/terms —
    Privacy: https://policies.google.com/privacy
  • Your own server — any OpenAI-compatible address the administrator
    enters (for example Ollama on your own network). Its terms are your own.
  • WordPress AI connection (WordPress 7.0+) — the request goes through
    WordPress’s own AI Client to the provider set in Settings → Connectors, under
    that provider’s terms and privacy policy.

CAPTCHA on forms (optional, off by default)

An administrator can choose a CAPTCHA in Stedica Surveys & Forms → Settings → Spam,
with keys from that service. Until then nothing is loaded. Once chosen, pages
that show a form load the service’s script from its own servers, and the
service receives the visitor’s IP address, browser details and how they use
the page. When the form is sent, your site sends the answer token and the
visitor’s IP address to the service to check it. Answers are never sent.

  • Cloudflare Turnstile — challenges.cloudflare.com.
    Terms: https://www.cloudflare.com/website-terms/ —
    Privacy: https://www.cloudflare.com/privacypolicy/
  • hCaptcha — js.hcaptcha.com, api.hcaptcha.com.
    Terms: https://www.hcaptcha.com/terms …

Installation

  1. Install through Plugins → Add New, or upload the ZIP via
    Plugins → Add New → Upload Plugin.
  2. Activate it. A short setup wizard opens: pick what you want to do,
    start from a ready-made survey, and get a survey link to share. You can
    skip it, and run it again from Settings → General.
  3. Put the survey on a page with the Stedica Survey block, the
    [stedica_survey id=”123″] shortcode, or the Elementor, Bricks or Divi
    element, or share its link.

FAQ

Do I need an account anywhere?

No. The plugin does not require registration and works entirely on your own
site. It contacts an outside service only for the optional features you switch
on yourself (webhooks, AI, a CAPTCHA, and Akismet if you use it), each
listed under External services.

Where are responses stored?

In your own WordPress database. Nothing is sent anywhere else.

Does the spam protection use Google reCAPTCHA?

No. It uses a hidden decoy field, a submission-timing check and a rate limit,
all handled on your own server. Nothing is sent to any third party, so there is
no external service to disclose and no consent banner to add.

What does “one response per person” actually record?

By WordPress account, it records the account id. By browser, a random value in
a first-party cookie that means nothing outside your site. By network address,
a salted one-way hash — the address itself is never stored and the hash
cannot be turned back into one. Surveys set to anonymous record none of these.

Is it accessible?

Stedica Surveys & Forms aims to conform to WCAG 2.2 level AA. Release 5.28.1 was
checked against the AA success criteria on the survey respondents fill in
(page, shortcode and embed) and on the main admin screens (Dashboard, All
Surveys, Builder, Results, Leads, Settings): automated checks for names,
labels, ARIA references, contrast, target size, headings and reflow, plus
hand testing with the keyboard alone. Release 5.41.0 then passed a full
screen-reader check of the survey and the admin screens with VoiceOver
(Safari, Mac) and NVDA (Windows). It has not yet been tested with disabled
users, or with JAWS, VoiceOver on iPhone or TalkBack.

What is covered:

  • Every field has a visible label tied to it; choice questions are grouped
    with their question as the group name; required questions say “(required)”
    in text, not only with a colour or an asterisk.
  • Everything works with the keyboard, with a visible focus outline and a
    skip link. Focus stays put when a choice re-draws the survey.
  • Errors: a summary at the top is announced, focus moves to the first
    missing question, and each missing question is marked and described.
    In list mode each item in the summary links to its question.
  • Images on the start and result screens take your description as alt
    text, filled from the Media Library when you pick them.
  • A text question that asks for a name, email, phone number or address can
    say so (Personal detail asked for), so the browser can fill in the
    respondent’s saved details and phones show the right keyboard.
  • Questions that appear or disappear through logic are announced.
  • Text, buttons and the offline-sync bar meet 4.5:1 contrast; targets are
    at least 24 by 24 pixels; the survey reflows to 320 pixels with no
    sideways scrolling (wide matrix tables scroll inside their own box).
  • Motion follows the device’s reduce-motion setting.

Known exceptions and alternatives:

  • Signature: drawing needs a pointer, so the question also takes a typed
    full name.
  • A quiz time limit (Premium, optional and off by default) is part of the
    test, so it cannot be turned off by the respondent (WCAG 2.2.1 allows
    this for real-time and essential limits). Warnings are announced.
  • Maps (GPS capture and the Premium Map shape question) use OpenStreetMap
    tiles, which carry no text alternative. Points can be added with the
    keyboard (arrow keys pan, Enter adds the point at the centre) and the
    result is given in text.
  • Your theme, your own survey text and images, and other plugins on the
    page are outside the plugin. Describe the images you add on the start
    and result screens in their Image description field.

Found a barrier? Report it on the plugin’s support forum and it is
treated as a bug.

Can respondents answer without an internet connection?

Yes, and it is switchable per survey. Open the survey in the builder and look
under Survey Settings for “Collect responses offline”. When it is on, answers
are stored on the respondent’s device and sync when the connection returns; the
Offline Sync Monitor shows what is still queued. When it is off, nothing is
stored on the device and no connectivity banner is shown.

Surveys created before version 5.0.0 have it on.

How much can a device hold offline?

These are the limits, as built and as tested in Chrome:

  • Responses waiting to sync: no fixed number. They live in the browser’s
    own storage, which on a current phone or laptop allows several gigabytes
    per site; answers without photos take a few kilobytes each.
  • Photos: up to 10 MB each (less if your server’s upload limit is lower),
    as JPEG, PNG or WebP. A bigger photo, as newer phone cameras take, is scaled
    down on the device before it is stored or sent: longest side 3,000 pixels,
    JPEG, usually 1 to 4 MB. A photo within the limit is kept exactly as taken.
  • Per response: up to 25 photos and 100 MB in total.
  • Uploads: up to 30 photos per 15 minutes from one internet address.
    Devices that share an office connection share that allowance; a device
    over it keeps the photos and tries again later.
  • Sync: 25 queued items at a time, repeated until the queue is empty.
    A photo the site refuses for good (too large, wrong type, too many in one
    response) is left out with a message, so it cannot hold up the rest.

What can make a device lose waiting responses:

  • Clearing the browser’s data, or answering in a private window.
  • Safari on iPhone and iPad deletes a site’s stored data when the site
    has not been opened for 7 days of Safari use. Collectors should sync at
    least every few days, or add the survey to the Home Screen (Share → Add to
    Home Screen), which Safari does not clean up this way.
  • A full device. When a phone runs out of space, the browser may clear
    site data. The survey asks the browser to keep its data once something is
    waiting to sync, but the browser decides.

If a survey page stays open for more than a day without a connection, reload
it once the device is online so syncing can resume; the waiting responses
are kept.

Does the plugin work without the paid extensions?

Yes. Everything documented above is in this plugin and is not gated. The
extensions add separate features; they do not unlock anything here.

Do notification emails work with my SMTP plugin?

Yes. The plugin sends through wp_mail(), which any SMTP plugin overrides in
the normal way. If notifications are not arriving, that is almost always the
site’s mail delivery rather than the survey: send failures are written to the
plugin’s error log, visible on Stedica Surveys & Forms → Plugin Health.

Can I let someone build surveys without making them an administrator?

Yes — the plugin adds a Survey Editor role with the survey capabilities and
nothing else.

Can I use it in my language, or help translate it?

The plugin is translated on translate.wordpress.org, and WordPress installs the translation for your site’s language by itself. Anyone with a WordPress.org account can help: open https://translate.wordpress.org/projects/wp-plugins/stedica-surveys/, choose your language and suggest translations; a language’s editors approve them. German, French, Brazilian Portuguese and Italian are the most wanted next; if you would like to be the editor for your language, say so in the plugin’s support forum.

Screenshots

Changelog

5.53.1

  • The Dashboard shows the new name, Stedica Surveys & Forms, and its main button reads Create Survey or Form.

5.53.0

New name: Stedica Surveys & Forms.
* The plugin is now called Stedica Surveys & Forms, in the Plugins list, the
admin menu, the screens and the manual. Nothing else changes: same plugin,
same address on WordPress.org, same settings and data.
* The description now covers forms: Entries, notifications, spam protection
and the link to Stedica CRM.

5.52.0

Developer release for Premium’s Stripe payments.
* Developers: new filter stedica_surveys_hold_delivery lets an add-on hold
back notifications, webhooks and CRM for a saved entry until it releases it.
* Developers: new filter stedica_surveys_submission_response; a ‘redirect’
to an address on this site sends the person there after Send.

5.51.0

Developer release for Premium’s user accounts and posts from forms.
* Developers: new filter stedica_surveys_normalize_settings lets an add-on
keep its own survey settings when a survey is saved.

5.50.0

Calculated fields you can trust.
* New: a Formula editor for Calculated Fields in the Builder (Calculation:
Formula, Insert an answer, Decimals). Until now a formula could only come
in with an imported form.
* Improved: when a form is sent, the server works every Calculated Field out
again from the answers and stores its own result, so a total can no longer
be changed in the browser.
* Improved: formulas are read by a small parser instead of being run as
code, the same in the browser and on the server, and rounding is the same
on both (1.005 to two decimals is 1.01).
* Fixed: a formula with a negative answer, such as {a} – {b} with b = -3,
gave no result.
* Developers: the stedica_surveys_formula_variables filter and
StedicaSurveyRuntime.registerFormulaVariables() add placeholders to
formulas (Premium: repeater totals). StedicaSurveyRuntime.evaluateFormula()
and Stedica_Formula::evaluate() work a formula out. The
stedica_surveys_entry_field_html filter now also gets the question.

5.49.0

Groundwork for more notifications, file uploads and save & resume.
* Developers: notifications can be extended. New filters
stedica_surveys_notification_messages (more emails),
stedica_surveys_notification_should_send (send only when answers match)
and stedica_surveys_notification_email (change any email before it is
sent), and the actions stedica_surveys_notifications_sections and
stedica_surveys_notifications_saved for the Notifications screen.
* Developers: the stedica_surveys_answer_text filter (how an answer reads in
emails, Entries and exports), stedica_surveys_entry_field_html (how a
field shows in Entries) and the stedica_surveys_delete_session_files action
(remove an add-on’s files with an entry).
* Developers: StedicaSurveyRuntime.registerFooterAction() adds a control
under the survey’s buttons, and question renderers get the session, the
AJAX address and nonce, and the online state.
* Developers: notification attachments keep a file name given as the array
key.
* Resend notification also resends add-on notifications whose conditions
the entry meets.

5.48.0

Spam & delivery for forms.
* New: Settings → Spam. A blocklist of words, email addresses, email and
website domains and IP addresses (or ranges), checked on the server for
every form entry. A match goes to Spam, or is refused if you prefer.
* New: form entries are checked with Akismet when the Akismet plugin is
active with a key (it can be switched off).
* New: an optional CAPTCHA on forms: Cloudflare Turnstile, hCaptcha or
Google reCAPTCHA v3. Off until you choose one and enter its keys.
* New: an entry put in Spam by these checks sends no emails and is not
passed to Stedica CRM, webhooks or add-ons. Marking it Not spam sends and
passes it on then, once.
* New: Delete permanently in the Spam folder, and an Empty Spam button.
* New: a REST endpoint for forms, POST /stedica-surveys/v1/forms/{id}/entries,
with the same checks, for headless sites and apps. Off until switched on
in Settings → Spam; servers use an access key, your own pages the
WordPress REST nonce.
* Developers: the stedica_surveys_entry_spam action and the
stedica_surveys_spam_reasons and stedica_surveys_spam_checks_apply filters.
* Fixed: the Stedica CRM panel on the Entries screen fits a 320px-wide
screen.

5.47.0

  • New: send a form’s entries to Stedica CRM (1.13.0 or later). On the
    Entries screen, open a form and use the Stedica CRM panel: one switch,
    fields matched to contact fields from what they hold, consent recorded,
    and the answers on the contact’s timeline. Choice questions can become
    contact fields in one click. Each entry links to its contact.
  • New: when a contact is deleted in Stedica CRM, their entries can be
    deleted too (off by default). Merged contacts keep their entries.
  • New: stedica_surveys_forms(), stedica_surveys_form_fields() and
    stedica_surveys_entry_crm_contact() for integrations, and admin_url in
    the entry payload.

5.46.0

  • New: hooks for add-ons on the Entries screen: extra buttons and side
    panels on an entry, list filters, columns and bulk actions, notices and
    activity rows; and a filter to attach files to the notification emails.
  • Stedica Surveys Premium 5.46.0 uses them to assign entries to your team
    and download an entry as a PDF.

5.45.0

Entries: an inbox for what people send through your forms.
* New: Entries, with Inbox, Unread, Starred, Spam and Trash folders, an
unread count in the menu, filters by form, date and source, and a search
through every answer.
* New: an entry page with all fields, the consent given and its exact
wording, where the person came from (with UTM parameters), notes for your
team, and an activity list of every email sent and every change.
* New: edit an entry’s answers; each change is recorded with the old and the
new value. Print an entry, or send its notification or confirmation again.
* New: bulk actions to mark read or unread, star, mark as spam, move to
Trash, restore, delete permanently and export the selected entries as CSV.
Spam and Trash are left out of Results and exports.
* New: a second team notification, and Cc and Bcc on both. A form’s standard
team email now links to the entry ({entry_url}).
* New: Address field (street, second line, city, state, postal code,
country), filled in by the browser where it can.
* New: “One section per page” display mode, so a form or survey can run
over several pages with Back and Next; Next checks only that page.
* New: All Surveys shows whether each row is a survey or a form, with a
Forms filter and an Entries button. The Share window says “form” for forms.
* New: a form field that fails its format check shows the reason in red
under it as soon as the person moves on.
* New for developers: stedica_surveys_entry_status_changed and
stedica_surveys_entry_edited actions.
* Fix: an offline-saved answer for a response that no longer exists on the
server showed a sync error on every page. It is now dropped; a saved
submission is sent again under a new response instead.

5.44.0

Forms. A survey can now be a form: contact, quote request, registration,
newsletter sign-up.
* New: “This is a” survey, quiz or form, in the Builder’s Settings. A form sits
flat on the page in the theme’s font, puts form fields first in the palette,
keeps its confirmation on screen and has its own button text and colour.
* New form fields: Name (full, first or last), Email, Phone, Website,
Paragraph, Time, Consent, Hidden field and Content block.
* New: fields can share a row (half, third, two thirds or a quarter); on
phones each takes the full row. Choice questions can show their options as
cards with a line of text each.
* New: answer rules for text (shortest, longest, pattern) and a message of
your own for a field left empty.
* New: after submitting, show your own message (it can repeat answers) or go
to another page.
* New: six form templates, including a contact form that switches between a
quick message and a consultation request.
* New: email, phone, website, time and text rules are checked on your server
as well as in the browser, and a form’s required fields are enforced there.
* New for developers: the stedica_surveys_entry_submitted action hands out one
documented payload per submission, after it is saved.
* Fix: a response is now checked and stored against the version of the survey
the respondent was shown, not one edited while they were answering.
* Fix: clicking from a changed text answer into another field lost focus, so
what was typed next went nowhere. The click now lands where it was aimed.
* Fix: near the bottom of a long page, each answer made the page jump.
* Fix: a form lists every field left to fix in one go, not format problems
first and empty required fields only on the next try.
* Fix: Results show an empty multiple-choice or consent answer as blank,
not as “[]”.

5.43.1

  • Fix: a survey set to a language that WordPress itself is not installed in
    (for example a Spanish survey on an English site with no Spanish WordPress
    files) showed its link page in English. The plugin now loads its own
    translation for the survey’s language directly.
  • Fix: with Polylang active, the survey language’s messages from the server
    (errors, thank-you text) came back in the page’s language.

5.43.0

A language for each survey.

  • New: Survey language, under Display & Quiz in the Builder. It sets the
    language of the buttons, messages and labels on the survey’s own link page,
    and in its embed and popup, so a Spanish survey on an English site (or the
    other way round) reads in one language. The questions are shown as you
    wrote them. On a page of your site, the page’s language is still used. The
    list shows the languages the plugin has a translation for on the site.
  • Fix: the progress bar label “Progress” was always in English.

5.42.1

Fixes found by testing on a fresh install.

  • Fix: the survey link page had no page title with block themes such as
    Twenty Twenty-Five, so the browser tab showed only the address and screen
    readers had no title to read (WCAG 2.4.2). It now shows the survey name and
    the site name.
  • Fix: the trial offer no longer shows on the setup wizard, which opens
    seconds after activation.
  • Fix: the Dashboard header translated the product name; it now always reads
    Stedica Surveys.

5.42.0

Welcome and setup wizard.

  • New: a setup wizard that opens once after activation on a new site. Four
    short screens: what the plugin does, what you want to use it for, a
    ready-made survey to start from (or a blank one) with an optional survey
    link and email for each response, and a last screen with the link and
    shortcode to copy. It can be skipped on every screen and run again from
    Settings → General. It does not open after updates, on bulk or network
    activation, from WP-CLI, or on sites that already have surveys.
  • Fix: surveys were always listed as Draft and the Dashboard kept saying no
    survey was published, although every survey with questions could be
    answered. A survey now counts as published once it has questions, and
    existing surveys are updated once.
  • Changed: the Dashboard’s Get started list has four steps. “Publish it”
    and “Put it on a page” became one step, “Share it”, done once a survey has
    its own link or is on a page.

5.41.0

Bricks and Divi.

  • New: a Stedica Survey element for Bricks Builder. Find it under General
    in the Bricks elements panel, pick a survey (or give its slug), and the
    survey shows on the published page. In the editor it shows a card with
    the survey’s name instead, so editing never starts a response.
  • New: a Stedica Survey module for Divi, working the same way. It uses the
    Divi 4 module system, so Divi 5 shows it through its backward
    compatibility.
  • Nothing changes on sites without Bricks or Divi: both load only when the
    builder is active.

5.40.3

  • Fix: a photo over the site’s upload limit (10 MB, or less on some servers)
    was stored offline, then refused at sync, and held up every response
    waiting behind it on that device. Such a photo is now scaled down on the
    device first (longest side 3,000 pixels, JPEG); photos within the limit
    are kept exactly as taken.
  • Fix: a photo the site refuses for good is left out with a message, so the
    rest of the queue still syncs. Online, it is no longer saved offline to
    fail again later.
  • Once answers are waiting to sync, the survey asks the browser to keep its
    stored data, so it is less likely to be cleared to free space.
  • New FAQ, “How much can a device hold offline?”: photos, responses, upload
    limits and what can make a device lose waiting responses.
  • Removed unused code from the admin screens.

5.40.2

  • Every admin screen can now be translated: the survey list, Add New,
    Results (filters, buttons, the Go-Live Reset box, question type names),
    Settings, the Offline Sync Monitor and Plugin Health used to show English
    on a site in another language.
  • Error messages respondents can see are translatable too.
  • Fix: the confirmation before clearing the Plugin Health log now appears.

5.40.1

  • The note shown for a question type that cannot be drawn on the page can
    now be translated, and is marked so add-ons find it in any language.

5.40.0

  • For extensions: the survey runtime can set several answers at once
    (StedicaSurveyRuntime.setAnswers), saved like answers the respondent gave,
    with unknown questions and empty values skipped. Stedica Surveys Premium
    uses it to fill in answers from a spoken or typed note.
  • The survey settings voice_dictation and voice_fill are kept on save.
  • Help translate Stedica Surveys into your language: see “Translations”
    under Frequently Asked Questions.

5.39.0

  • Version number bumped to match Stedica Surveys Premium 5.39.0. No changes
    in the free plugin itself.

5.38.1

  • Builder: a question that shows an earlier answer ({answer:…}) is titled
    with that question’s label in brackets, “Is [Store name] open?”, in the
    question list, the logic and branching rule lists and the preview. The
    label you edit keeps the token.
  • All Surveys: the rule count includes branching rules.

5.38.0

Import a paper or PDF form with AI.

  • New: Add New → Import a paper or PDF form. Upload the form as a PDF, or as
    photos or scans of its pages, and the AI provider connected in Settings → AI
    writes it out as a survey: the same questions in the same words and order,
    with their options, and skip instructions as branching and show rules. Anything the AI
    was unsure about is listed in the preview, and nothing is created until you
    click Create this survey. Photos are made smaller in the browser first; the
    files are sent to your provider and not kept on the site.
  • AI requests can now include PDF files (Anthropic, OpenAI, Google Gemini and
    the WordPress AI connection). Your own OpenAI-compatible server is sent
    photos only.

5.37.0

Import an XLSForm.

  • New: Add New → Import an XLSForm. Read an .xlsx form made for ODK,
    KoboToolbox, SurveyCTO or Ona and check a preview before the survey is
    created. Groups become sections; select_one, select_multiple, rank, text,
    integer, decimal, range, date, image and acknowledge questions are carried
    over with their choices, required flags, hints, defaults and number limits;
    relevant conditions become show rules and ${name} references become answer
    piping. Anything that cannot be carried over (calculations, repeats, time,
    barcode, choice filters) is listed in the preview. The file is read once and
    not kept.
  • Surveys made from a template, an AI draft or an import can now carry show
    rules and answer piping from the start.
  • Fixed: when a show rule hid a question, a question shown because of that
    question’s answer (a follow-up to its “Other” option, say) stayed on screen
    until the next answer was given. It is now hidden at once.

5.36.1

  • Developer: new action stedica_surveys_schema_saved( $survey_id, $schema,
    $version_id ), fired after the Builder saves a survey. Premium uses it to
    keep its KPI Risk Engine in step with the Builder’s KPIs.

5.36.0

Field data quality, part 2. Hooks for Premium’s location at start and end and
quality per collector; nothing changes in the free plugin on its own.

  • Fixed: a Builder tab open on a survey that had since been deleted could
    still save, adding a version to a survey that no longer exists. The save is
    now refused with a message.
  • Fixed: in CSV exports a negative number (a longitude, a score below zero)
    was saved with a leading apostrophe, so spreadsheets read it as text. Plain
    numbers are now left as they are; other cells starting with -, =, + or @
    are still protected against formula injection.
  • The survey setting record_location (Premium: Record location at start and
    end) is kept when a survey is saved, as show_scorecard is, so it survives a
    save made while Premium is not active.
  • Developers: filters stedica_surveys_submission_answers (clean or remove a
    meta answer before it is saved) and stedica_surveys_quality_report (add to
    the Response quality report); StedicaResultsRuntime.registerQualityPanel()
    and StedicaBuilderRuntime.registerSettingsSection(); the front-end events
    stedica:start, stedica:step, stedica:answer and stedica_survey_reset now
    carry the survey’s instanceKey; quality flags filters see each response’s
    user_id.

5.35.0

Field data quality. Stedica Surveys and Premium now share one version number.

  • Fixed: a response collected offline was timed and dated by when it synced,
    so a day’s fieldwork could look like responses a few seconds long, and be
    flagged as “Completed unusually fast”. The device now sends when the
    respondent really started and submitted, corrected for a wrong device
    clock, and the speed check and the response view use those times. The
    server’s own times are kept as when the response reached the site.
  • Fixed: the next response started in the same visit after a submit, or a
    draft restored from the device, could be saved without its Surveyor (the
    logged-in user), and the next response lost answers prefilled from the link.
  • New survey setting, off by default: Record how each response was answered.
    It saves the seconds spent on each question and the kind of device (phone,
    tablet or computer, with the operating system and browser family, never the
    full browser details) with each response. Shown when you view a response,
    and included in personal-data export and erasure. The field templates
    switch it on.
  • Response quality has two new flags: Questions answered too fast to read
    (surveys that record how responses were answered) and Same answers as
    another response. The flags now also show at the top of a response when
    you view it.
  • CSV and Excel: captured_started_at and captured_submitted_at columns once
    any exported response has them, and active_seconds and device on surveys
    that record how responses were answered.
  • Developers: Stedica_Results::quality_report() and quality_flags_for();
    filters stedica_surveys_quality_flags, stedica_surveys_submission_problems
    (refuse an answer on the server) and stedica_surveys_record_paradata;
    StedicaSurveyRuntime.registerAnswerCheck() refuses an answer in the browser
    on Next and on Submit, in one-page and step mode.
    Database 3.8.0 adds two columns to the sessions table.

5.34.0

A hook for add-ons on the Results screen.

  • Developers: Stedica_Abilities::summary() returns the get-results summary
    of a survey under every Results-screen filter, including add-on filters.
    Stedica Surveys Premium 5.31.0 uses it for insights and chat with results.
  • Audit log: AI events read “AI”, not “Ai”.
  • Developers: filter stedica_surveys_ai_pre_json answers an AI request without
    calling the provider (for tests, recorded replies and caches).

5.33.0

More for AI assistants, and you decide what they may change.

  • Ten new abilities, fifteen in all: get one response in full, list the
    written answers to a question (with search), drop-off by question, the
    views-to-completions funnel, a guide for assistants, copy, rename and
    share a survey, and delete responses or a whole survey.
  • Settings → AI → AI assistants now has two switches, both off: Allow
    changes (create, copy, rename, share links) and Allow deletions. An
    ability that is off is not offered to assistants at all. Deleting also
    needs the assistant to send an explicit confirmation.
  • Changed: creating a survey through an assistant now needs Allow changes
    turned on. If you used it before, turn it on in Settings → AI.
  • Every change made by an assistant is in the Audit log, and Go-Live Mode
    blocks all of them.
  • Abilities carry read-only and destructive annotations, so on WordPress
    7.1 an assistant can ask for read-only ones only
    (meta[annotations][readonly]=true).
  • A guide for assistants ships with the plugin in
    skills/stedica-surveys/SKILL.md, and the get-guide ability returns it.
  • Fixed: get-survey now reports one-question-at-a-time surveys as step mode.
  • Developers: Stedica_Abilities::meta() gives add-on abilities the same
    switches; filter stedica_surveys_ability_response; action
    stedica_surveys_responses_deleted; Stedica_Admin::delete_survey(),
    Stedica_Admin::delete_responses() and Stedica_Results::dropoff().

5.32.1

Accessibility fix.

  • On a survey with all questions on one page, pressing Tab after typing an
    answer now moves to the next field. Before, keyboard focus jumped back to
    the top of the page (WCAG 2.4.3, focus order).

5.32.0

Hooks for add-ons.

  • Add-ons can add settings to a question in the Builder and content under a
    question in the survey, and store extra data with the response. Stedica
    Surveys Premium 5.29.0 uses them for AI follow-up questions.
  • The server can check that a request comes from the respondent who owns an
    open response.

5.31.1

Fixes.

  • Rating questions use one scale everywhere. The Builder has a Rating scale
    setting (lowest and highest), and Test mode and the preview card now show
    the same input as the published survey instead of five stars. Empty
    settings keep the 1 to 10 scale surveys already use.
  • The survey states the rating scale in words. A rating or number outside
    the question’s limits is no longer saved: it stays on screen with the
    reason, and Submit lists it. Number messages are translatable.
  • The Results screen is translatable: headings, charts, the response view,
    funnel, drop-off and quality checks.

5.31.0

Accessibility: the last two WCAG 2.2 AA gaps are closed.

  • Start and result screen images have an Image description (alt text) field
    in the Builder, filled from the Media Library’s alt text when you pick the
    image. Leave it empty for a decorative image.
  • Text, prepopulated and demographic questions have a Personal detail asked
    for setting (name, email, phone, organisation, address parts, country,
    website). It sets the browser’s autofill purpose (WCAG 1.3.5), and email,
    phone and website fields get the matching keyboard on phones.
  • The error summary shown when required answers are missing now links each
    item to its question in list mode.
  • The surveyor name field asks the browser for a name.

5.30.0

One AI key for the whole site.

  • New: on WordPress 7.0 and later, Settings → AI offers WordPress AI
    connection
    . It uses the provider and key set in WordPress’s own Settings →
    Connectors, through the WordPress AI Client, so the key lives in one place.
    The model is optional: WordPress picks a capable one. Sites on WordPress
    6.4–6.9, and anyone who prefers it, keep the existing providers.
  • New for add-ons: the AI connection can send images. The AI Images add-on
    4.4.0 uses it to analyse photos with any connected provider, not only OpenAI.

5.29.0

Multiple choice can take more than one answer.

  • New: tick Allow more than one answer on a Multiple Choice question and
    respondents get checkboxes (“Choose all that apply”). Most answers
    allowed
    caps the count, and Only answer on an option such as “None of
    the above” clears the others when it is ticked.
  • Logic, branching and result rules on such a question match when their
    answer is among those ticked; quiz points add up across the answers.
  • Results: shares on a multi-select chart are out of the people who answered,
    so they can add up to more than 100%. CSV and Excel show the answers in one
    cell, separated by semicolons (ranking answers too, in rank order).
  • The starter templates that were written with multi-select questions now
    work as intended; before, respondents could pick only one answer.
  • The Builder’s preview and Test mode show checkboxes or radio buttons to
    match what respondents will see.
  • The “(required)” that screen readers hear after a question, and the “and”
    joining a piped list of answers, can now be translated.

5.28.4

Clearer description.

  • The plugin description now says what it does today: quizzes, lead
    funnels, result screens, funnel reports and AI with your own key, and
    what Premium and the add-ons add.
  • Once a site has 10 responses, the Stedica Surveys Dashboard shows
    administrators a small panel asking for a WordPress.org review, with a
    link to the support forum. It never appears as a notice on other screens,
    and Hide removes it for good.

5.28.3

The Builder can be translated.

  • Every Builder label, button, hint, warning and message now comes from
    translatable strings (wp.i18n in the browser, gettext on the server),
    including the start page, the question inspector, logic and branching,
    outcomes, the preview and the keyboard shortcut list.
  • Question type names and descriptions, the admin menu items and page
    headings, the “Section 1” default and the plugin’s AJAX error messages
    are translatable too.
  • Counts use proper plural forms (“1 condition”, “2 conditions”).
  • Fix: a few Builder texts built from survey content (the warnings
    tooltip, the KPI assignment list and the anonymous responses notice)
    are now escaped before they are shown.

5.28.2

Translation groundwork.

  • The in-plugin manual can now be translated: its text was not picked up
    by WordPress’s translation tools before (the text domain was passed as a
    variable), so translate.wordpress.org never offered it.
  • A translation template (languages/stedica-surveys.pot) ships with the
    plugin for translators working outside translate.wordpress.org.

5.28.1

Accessibility release: surveys and admin screens checked against WCAG 2.2 AA.

  • A missing answer is now marked on the question itself (aria-invalid and a
    message tied to the field), not only in the summary at the top.
  • Questions shown or hidden by logic are announced to screen readers. The
    question list is no longer a live region that re-read itself on every
    change.
  • Matrix questions keep focus on the chosen answer (they lost it on every
    click) and their radio buttons are 24 pixels. Wide matrices scroll inside
    their own box on small screens.
  • Signature questions take a typed full name as an alternative to drawing.
  • The hosted survey page has a page heading (h1).
  • Reset and Sync buttons and the dashboard’s Create Survey button now meet
    4.5:1 contrast. The builder uses the same darker teal as the survey.
  • Labels on the Results filters and the builder’s rule templates and
    availability dates are tied to their fields; the builder’s survey title is
    an h2 under the screen heading.
  • A visually hidden legend no longer widens the page on narrow screens.
  • New: an accessibility statement in the FAQ.

5.28.0

Groundwork for field-team tools in add-ons, and one fix.

  • Fix: a response saved on the device while offline, before the survey
    had reached the server, could be refused as spam when it synced (it was
    sent too soon after its session was created). The sync now waits out the
    few seconds the spam check needs.
  • Developers: StedicaSurveyRuntime gets restart() (start a new response
    with known answers, e.g. the next visit on a case list), setMeta()
    (attach hidden __-prefixed values to the response), findInstance() and
    instanceKeys(). A stedica_survey_queued_offline event fires when a
    response is saved on the device to send later.
  • Developers: the Results screen gets window.StedicaResultsRuntime
    (registerColumn, registerResponsePanel) and the filters
    stedica_surveys_results_filters, stedica_surveys_session_where,
    stedica_surveys_results_sessions and stedica_surveys_single_response,
    plus the stedica_surveys_results_filter_fields action.
  • Developers: stedica_surveys_normalize_question lets an add-on keep its
    own settings on a question when a survey is saved.

5.27.0

Groundwork for quiz tools in add-ons. Nothing changes for your surveys.

  • Developers: the front-end runtime (window.StedicaSurveyRuntime) gets
    registerQuestionFilter (ask a subset of the questions, or reorder them),
    registerStepGuard (hold the flow after a valid answer, e.g. to show
    whether it was right), registerOutcomeFilter (change the result the
    browser works out) and panelNames(); every registered panel now renders
    above the questions, and a panel can submit what is answered so far.
  • Developers: Stedica_Outcomes::resolve() takes the survey id, and the
    stedica_surveys_resolve_outcome filter receives it as a fourth argument.

5.26.0

AI assistants can work with your surveys, through the WordPress Abilities API.

  • Five abilities on WordPress 6.9 and later: list surveys, get a survey, get
    results (totals, completion rate, result screens, answer counts, averages,
    recent written answers), list responses (up to 100 a call, answers only,
    no respondent accounts) and create a survey (a draft, checked exactly like
    an AI draft on Add New).
  • With the MCP Adapter plugin they appear as tools for Claude, ChatGPT,
    Cursor and any MCP client; they also work through
    /wp-json/wp-abilities/v1.
  • They need the same permission as the Results screen and Builder, run as the
    signed-in user, and creating a survey is audit-logged and blocked in
    Go-Live Mode. This plugin sends nothing anywhere for them.
  • Settings → AI shows what is available and the address to connect to.
  • Developers: Stedica_Builder::insert_survey() creates a survey through the
    same transaction and validator as Add New; filters stedica_surveys_abilities
    and stedica_surveys_abilities_mcp_public.

5.25.0

Write surveys and quizzes with AI, using your own key.

  • New Settings → AI tab: connect Anthropic (Claude), OpenAI, Google Gemini or
    your own OpenAI-compatible server (Ollama, LM Studio, vLLM) with your own
    API key, or define STEDICA_AI_KEY in wp-config.php. Test the connection
    from the same screen. Off until an administrator connects a provider.
  • Add New → Write it …