Different counters answer different questions
| Signal | What it can tell you | What it does not prove |
|---|---|---|
| Menu opens | Recorded openings of the menu | Unique diners or visits caused by Google Search |
| Dish views | Recorded interest in dish details | An intention to buy or an ingredient preference |
| Submitted orders | Requests recorded by the ordering workflow | Completed service or collected payment |
| Order item totals | The amounts recorded on those orders | Card settlement, profit or money received |
Keep the comparison consistent
The dashboard ranks the five most viewed dishes by recorded detail views. With Pro or Business, it also ranks dishes by units submitted in orders, including orders later cancelled or rejected. These quantities show what was requested, not sales or payments received.
Both rankings follow your selected location and period. If older activity lacks dish detail, the report shows partial coverage instead of reconstructing figures. A top-five list is only part of the menu, so its sum need not equal every event in the period.
Use the same location and date window before comparing activity. The reports use the location’s calendar and timezone. The 7- and 14-day views can compare the preceding period when the available history permits; the 30-day view does not invent a previous 30-day baseline.
An empty period stays at zero. A zero baseline does not support a meaningful percentage-growth claim. Business can compare authorized locations, but different opening hours, promotions or service volumes can explain a difference.
Illustrative example: 120 menu opens and 6 orders
Imagine that one location shows 120 menu opens and 6 submitted orders for a week. These are invented figures to explain the report, not a restaurant’s results or a performance promise.
You can say that those events were recorded in the period. You cannot conclude that 120 people visited, that six of those people bought something or that the order totals were collected. The counters do not track one shared user cohort, so dividing them does not establish a conversion rate.
Before changing the menu, check whether ordering was enabled all week, whether service was paused or dishes sold out, and whether the QR identified a table. Review order states and reconcile payments in the system your restaurant uses to collect them.
Turn an observation into a small check
If a dish attracts views but few orders, review its availability, description and options before changing its price. Note what changed and when, then compare a similar service period. Aggregate counters are not a tracked person-by-person conversion funnel, so they cannot establish that the same guests moved through every step.
Questions before you start
Can I use menu opens to measure this platform’s SEO?
No. Restaurant menu activity and acquisition for the Menuviora website are different datasets. Search performance needs a published property and search measurement; opening a menu does not identify a Google visit.