Survey for TYPO3

Quick polls on the website generate engagement that comment sections never deliver

In practice, blog posts with a comment function achieve less than 1 percent interaction. A poll (“Do you agree?”, “Which option do you prefer?”) reaches 5 to 15 percent, because the barrier is lower: one click instead of typing a text. The TYPO3 Umfragetool (the extension key is German for “survey tool”) brings simple polls directly into the CMS. Editors create polls in the backend (question, answer options, single or multiple choice, how results are displayed), embed them as a content element and see the results in real time. For a quick read on opinion, that is enough. For scientific or complex surveys, we recommend the LimeSurvey integration, which offers far more powerful question types and analysis.

Typical uses are reader polls, event feedback and member votes

The most common scenario is a reader poll on a news or blog page. A trade magazine asks: “Which feature would you most like to see in TYPO3 v14?” with five answer options. Readers click their choice and immediately see the percentage breakdown. This creates engagement, gives the editorial team a sense of what its audience thinks and adds an interactive element to the article that increases time on page.

A second scenario is event feedback. After a conference or webinar, participants see a poll on the TYPO3 website: “How would you rate the event?” (excellent / good / fair / poor). It does not replace a detailed feedback questionnaire, but it is a quick satisfaction check that far more participants complete than an email survey.

Third scenario: votes in associations and committees. A professional association lets its members vote on a logo redesign. Three designs are up for selection, and each member has one vote. Combined with fe_login, the setup ensures that only registered members vote and that each member takes part only once.

Polls are stored as Extbase records with vote counters

The Umfragetool defines two Extbase models: Poll (question, description, start and end date, multiple-choice flag) and Option (answer text, vote count). A poll contains several options. Votes are stored as a counter (an integer increment) on the option, not as individual records per participant. That keeps the database lean and performance high, but it also means that individual answers cannot be traced.

In the frontend, the extension renders a form with radio buttons (single choice) or checkboxes (multiple choice). On submission, the counter of the selected option is incremented, and the results appear as a horizontal bar chart with percentages.

To prevent multiple votes, the extension relies on cookie-based duplicate detection: after voting, a cookie is set that blocks a second vote. That is not real protection (cookies can be deleted), but it is sufficient for opinion polls without formal requirements. Binding votes require the combination with fe_login, which allows checks against the fe_users table.

Weak spots are manipulation and missing analysis features

The biggest problem with open polls is how easily they can be manipulated. Without a login, a visitor can delete the cookie and vote again. In incognito mode, the cookie lock does not work at all. Anyone who needs reliable results has to tie the poll to fe_login. For low-threshold opinion snapshots (“What interests you?”), on the other hand, the cookie solution is acceptable.

Second problem: missing analysis features. The Umfragetool stores only totals: no trends over time, no segmentation by user group, no cross-tabulation. If the analysis has to go beyond “63% choose option A”, LimeSurvey or a dedicated survey tool is the better choice.

Third issue: design customization. The bundled templates are functional but not built for modern UI expectations. Anyone who wants polls in a clean design with animations (bars filling up, percentages counting up) has to override the Fluid templates and add their own CSS and JavaScript.

TYPO3 v12 is supported, and for more complex surveys LimeSurvey is the better choice

The Umfragetool runs stably under TYPO3 v12. For v13, the plugin registration needs an update. Because the extension is technically lean (two Extbase models, one controller, one Fluid template), the migration is straightforward. Gosign recommends the extension for simple polls with three to five answer options. As soon as question types such as Likert scales, open text fields, matrix questions or conditional logic are needed, a LimeSurvey integration is the more professional solution.