Emovart Docs
Insights

What are feedback analytics insights?

How to read the reactions and comments your visitors leave — and turn them into a better help center.

Last updated on July 9, 2026

Every article on your Emovart site ends with a small question: "Did this answer your question?" Feedback analytics is where all of those answers come together — a dedicated view inside your console's Insights tab that shows which articles delight readers and which ones send them away frustrated.

What are article reactions?

The reaction box sits at the bottom of every published article and offers three emoji faces — one happy, one neutral, one sad. A single click is all it takes, so even readers in a hurry leave a signal.

Article reaction box
Article reaction box

Right after reacting, visitors are invited to add an optional written comment. This is where the gold is: a sad face tells you that something is wrong, the comment tells you what.

Optional comment prompt
Optional comment prompt

Every reaction and comment is stored per article and rolled up in the console, so one glance shows you exactly where readers are struggling.

Feedback analytics overview
Feedback analytics overview

Dashboard

Open Insights → Feedback analytics to see the big picture: total reactions across your site, how they split between happy, neutral, and sad, and how the mood develops over time. The time-range picker makes it easy to compare, say, the month before and after a documentation overhaul.

Reading the article feedback table

Below the dashboard, every article gets its own row with its reaction counts and a calculated satisfaction score, so you can sort your entire knowledge base from "loved" to "needs work."

Satisfaction score column
Satisfaction score column

How the satisfaction score works

The satisfaction score condenses an article's reactions into a single percentage. Happy reactions count fully, neutral ones count half, and sad ones count zero — so an article with 8 happy, 2 neutral, and 0 sad reactions scores 90%. As a rule of thumb, anything above 80% is doing its job, while a score below 50% is asking for a rewrite.

Data confidence badges

A 100% score based on a single reaction means very little. That's why each row also carries a confidence indicator — Low, Medium, or High — based on how many reactions the article has collected so far. Treat low-confidence scores as anecdotes, not verdicts, and wait for more data before rewriting a page over one sad face.

Drilling into a single article

Click any row to open that article's detail view. There you'll find its full reaction breakdown, every comment left on it, and two maintenance actions: a button to reset the article's reactions and one to remove its comments — handy after a major rewrite.

The comments table

Written comments get their own table showing the comment text, the article it belongs to, the reaction it came with, and when it was left. Skim it once a week: it's the closest thing to a direct line from your readers, and nobody had to open a support ticket to reach you.

Keep review bias in mind

Feedback boxes attract extremes. A reader whose problem was solved usually just closes the tab, while a frustrated one is far more motivated to click the sad face and say so. Expect your raw numbers to skew a little negative and read them accordingly: the trend over time matters more than any absolute score, and even your best articles will collect the occasional 😕.

Related articles

Was this article helpful?