Feedback widget

A feedback widget is a function on a website that makes it possible for visitors to leave comments directly on the page they are on. It can for example be used to collect ratings, smileys, comments or answers to short questions. With esMaker's feedback widget the answers are collected directly in esMaker, where they can be followed, analysed and combined with other surveys and measurements.

A feedback button is a clickable button on a website that opens a form or a question where the visitor can leave feedback. The button makes it easy to capture views in direct connection with the visitor's experience, without the person first needing to look for a contact page or a separate form.

A feedback button is usually the visible part the visitor clicks on, while feedback widget describes the whole function that opens when the button is used. In practice the terms are often used for the same type of solution: a simple way to collect feedback directly on a website.

Feedback directly on the website makes it possible to understand the visitor's experience while it is still current. Web analytics can show what a visitor does, for example which pages are visited or where someone leaves the website, while feedback can complement the picture by answering questions such as why the information was not enough, what was difficult or what the user was missing. That gives a better basis for prioritising improvements to content, services and user experience.

A feedback widget can be used to collect views on many different parts of a website. Common uses are to find out whether the visitor found the right information, measure how usable a page is experienced, discover problems or ambiguities, evaluate new content, collect suggestions for improvement, follow up the experience of digital services or flows, and capture spontaneous comments from visitors. The questions can be adapted to the purpose of the page where the widget is used.

The most important thing is that you contribute goals, target group and basic information about what you want to understand. Entergate then helps you shape the setup, questions, distribution and reporting. You therefore do not need finished questions, finished reports or technical knowledge from the start. We can guide you through the process and help with the practical work, while you contribute operational knowledge and decisions about what the survey should be used for.

Good questions are short, clear and linked to what the visitor has just done or read. Examples are asking whether the visitor found the information they were looking for, how usable the page was experienced, how easy it was to do what the visitor came for, what was missing and what you can improve. A good setup is often to start with a quick question and then give the visitor the opportunity to expand their answer in free text.

Yes. With esMaker's feedback widget you can collect feedback on specific pages on the website. That makes it possible to ask different questions depending on the page's purpose – on a support page you can for example ask whether the information solved the problem, while an information page can ask whether the visitor found what they were looking for. Page-specific feedback also makes it easier to understand which part of the website a comment relates to.

In esMaker's feedback widget you can use different types of answers depending on what you want to measure or understand, including open comments, ratings, smileys and scales. Structured answers make it easier to follow results over time, while open comments give more detail about why the visitor answered as they did. By combining both you get both a measurable result and an explanation behind it.

esMaker's feedback widget makes it possible to ask questions directly on the website and collect the answers in esMaker. You create the questions you want to ask, the feedback button is shown on the page where you want to collect views, the visitor opens the widget and leaves their answer, the answers are collected in esMaker and you follow, filter and analyse the result as a basis for improvements. In that way the feedback from the visitor goes directly into the same environment where you can continue working with analysis and reporting.

Yes. esMaker's feedback widget can be adapted so that it fits the website's design and context. You can among other things adapt colour, placement, icon, text and which questions are shown. That makes it possible to let the feedback button feel like a natural part of the website instead of a separate tool.

Yes. Answers from esMaker's feedback widget can be followed in real time. In esMaker you can continue working with the results by among other things filtering answers, making selections, combining questions and creating reports or dashboards. That means you can follow developments continuously instead of waiting for a separate survey to end.

Yes. esMaker has support for AI-based analysis of free-text answers. That is particularly useful when you collect many open comments and need a better overview of the material. The AI analysis can be used together with esMaker's other functions for filtering, selection, analysis and reporting, which makes it easier to continue working with large amounts of qualitative feedback.

Yes. Feedback from the website can be handled together with other surveys and measurements in esMaker. That means you do not need to treat website feedback as a separate data source; it can be part of a larger piece of work with, for example, customer feedback, user surveys, employee surveys or other ongoing measurements. That gives a more collected environment for analysis and reporting.

Yes. esMaker's feedback widget is part of esMaker and can be used in GDPR-adapted work with website feedback. How a specific feedback collection should be designed still depends on which information you choose to collect, whether personal data is requested and which routines your organisation has for processing and storing data. For more sensitive uses the setup should always be adapted to the organisation's own data-protection requirements.