Skip to content
Venue MenusDocumentation

Operations and integrations

Analytics

Understand menu interest without tracking individual guests.

For Owners and staffReviewed September 15, 2026
Open in Studio

Before you begin

A published menu receiving web, QR, or embed requests.

What changes

Viewing analytics does not change menus. Overview and Analytics report request totals from the stored rolling summaries.

What is counted

A menu view is a qualifying request for a public web or embedded menu. Opening a Venue Menus QR code records the QR source and is included in the overall view count. Overview summarizes the last seven UTC calendar days, including today.

Analytics shows request activity, not orders, revenue, or foot traffic. Use Square Sales for connected transaction reporting.

Privacy boundaries

Guest menu analytics uses no cookies and does not claim to identify unique visitors. Studio previews suppress view counting, so checking your own draft does not inflate the total.

Interpret the totals

One guest can create several requests, and cached or blocked requests can affect counts. QR scans are a source within menu views rather than an additional audience total. Missing summaries display an em dash instead of inventing zero.

Compare consistent date windows and publication status. Treat these figures as directional operating context.

Limits and boundaries

Menu views are requests, not unique people. QR scans are included in views; the Overview summary covers seven UTC calendar days.

If something goes wrong

An em dash means a summary is unavailable, not zero. Confirm publication and use a longer observation window before diagnosing low traffic.

Still stuck? Email Venue Menus support with the location, menu or screen name and the action you were taking.