A no-login poll lets anyone in the room vote by scanning a QR code on the venue screen and answering in their browser, with no app install and no sign-in. In Sociana the answers land in the same occasion as in-app answers, so the venue screen and the reports show one result. The QR matters because every plenary has people who never installed the app, and a poll that only works inside the app quietly excludes them.
This post explains what the QR changes, what it does not, and how to measure it without fooling yourself.
Why not simply ask everyone to install the app?
You can ask. Some will not, and the reasons are ordinary: a full phone, a poor signal in the hall, a guest who arrived five minutes before the keynote, a partner who is only there for one session. Asking a room to install something while the stage waits is the wrong moment to do it.
The QR offers a second door that costs a person a few seconds. The app stays the better experience, with points, feed and agenda, and the no-login page is the fallback that keeps the room in the conversation. The two are designed to work together, not to compete.
How does a no-login poll work in Sociana?
Live polls and voting run on one engine, whether a participant answers inside the branded attendee app or on a public web page. A poll can be a single question, a multi-question quiz, a word cloud or a vote between nominees. The sequence is short:
- The organiser or an in-app Manager with trigger rights starts the question from their phone.
- A public web link and QR code appear for the room, often on the venue screen.
- Participants answer in the app or in the browser.
- Results update live on the venue screen designed for projection.
- Because no-login voting merges into the same occasion, reports and the leaderboard see one set of answers.
Participation can award configurable points on the unified leaderboard for in-app members. That is the gentle nudge: people who vote through the browser can see what the app would have given them.
What does the no-login door not do?
Being candid about limits is part of using it well.
- It is anonymous by design. A browser answer cannot be tied to a named member unless you build a separate flow for that. If you need to know who answered, use the in-app poll for that question.
- It is open to whoever has the link. The QR is public. Plan for duplicates and for people outside the room. Close the poll when the question ends, and keep votes that matter, such as awards, on a controlled route.
- It depends on a connection. A hall with poor mobile coverage can slow browser answers. Check the venue before you plan a poll that needs every phone.
- It does not replace attendance. Voting is not the same as being there. Accepted attendance is a separate record, taken by scan at an activity.
Because of the second point, we treat awards and formal votes differently from a “which topic should we cover next” poll. Choose the door to match the stakes.
When should you use which door?
| Situation | Better door | Reason |
|---|---|---|
| Town hall question, opinion or temperature check | No-login web | Lowest barrier, anonymity helps honesty |
| Quiz with points and a leaderboard | In-app | Points attach to a named member |
| Awards audience vote | Defined per occasion | Needs a clear rule on eligibility and duplicates |
| Mixed room where half have not installed | Both, same question | One result, two doors |
| Group-specific question for partners only | In-app, with group scoping | The web page is open to anyone with the link |
Group polls restrict a question to chosen groups and report results per group. That is only possible when the participant is identified, which is one more reason the in-app poll exists.
How do you measure whether the QR helped?
This is where most reports go wrong. “We had 600 votes” means nothing without a denominator. For a poll, there are three honest ways to express it:
- Of the people present. Votes from unique respondents divided by accepted attendance for the session. Browser respondents cannot be de-duplicated per person, so state that you counted answers, not people, or use one answer per device as an assumption.
- Of the people activated. In-app voters divided by those who activated the app.
- Door split. What share of answers came through the app and what share through the browser. This is a descriptive figure, not a rate.
Run the comparison on your own occasion: record the share through each door, and notice whether the first question after the QR is shown behaves differently from the last.
Our glossary defines participation rate, the general metric.
Practical tips for a smooth poll
- Put the QR on the screen for the whole question, not for a few seconds, and read out the short URL once.
- Test the QR from the back row at the venue before the day.
- Keep the first poll of the day simple and fun so people learn the routine.
- Have a Manager trigger and close each question so results are final.
- For quizzes, announce how points are awarded and what happens to ties.
- Exclude staff from results and leaderboards where you want honest partner numbers.
Our case studies show the pattern in practice. The HCCB Partners Meet 2026 ran live polls alongside group-scoped content, and plenary polls at a partner meet are the textbook case for a QR on the venue screen.
Frequently asked questions
Do guests need a Sociana account to answer? Not for a no-login poll. They scan the QR and answer in the browser.
Do web answers and app answers appear together? Yes. They merge into the same occasion, so the venue screen and the reports show a single result.
Can I stop duplicate votes? Design for it: close each question promptly, use the in-app poll when identity matters, and state your counting rule in the report.
Is it suitable for awards? It can be, if the occasion defines who may vote and how duplicates are handled. Confirm the rule with the team before the day.
For the matching glossary entry, read no-login poll. If you want to see the flow on your own guest list, talk to us.