For restaurants / Analytics

Visitors, and whether they booked.

Visitors, pages, where they came from, and the reservations the site produced — counted without cookies, with a conversion rate a restaurant can act on.

  • Seven, thirty or ninety days, with deltas
  • No cookies, no profiles, Do Not Track honoured
  • Google Analytics, Tag Manager and Meta alongside
Cartelier StudioAnalytics · last 30 days
WebsiteAnalyticsSettings
Visitors

1,284

▲ 18%
Page views

3,916

▲ 12%
Reservations

96

▲ 24%
Conversion

7.5%

Visitors per day
Pages
/42%
/menus31%
/reservations18%
Came from
google.com48%
direct33%
instagram.com11%

The numbers that matter to a restaurant

Not pageviews for their own sake: visitors, the pages they read, where they came from, and how many of them booked. Conversion is stated as reservations per hundred visitors, against the same window a week or a month earlier.

Counted honestly

No cookies and no profile. A visitor is a daily-rotating hash, so we can count unique visitors per day and nothing more. Do Not Track is honoured and bots are dropped. If you want Google Analytics or a Meta pixel as well, they load alongside.

What guests did

Menu views, bookings started, reservations completed, inquiries sent, newsletter signups. Enough to know whether the menu page is doing its job, and whether the booking flow is losing people.

Free to use. No commissions.

Your restaurant is probably already in the archive. Claiming it opens the studio on your existing record.