Which events matter on a restaurant site?

Menu views, allergen filter use, booking clicks, enquiry submits, and outbound clicks to OpenTable or ResDiary.

Should you wait for a data team?

No. A short, named set of events at launch beats a perfect taxonomy that never ships.

track this

technical deliveryApr 27, 2026by LemonOctopus

Day one should tell you if diners reached the menu and the booking button — not a soup of events nobody named.

Analytics fails when everything is tracked and nothing is trusted. Launch with a small set tied to covers: menu, book, enquire.

Name events like a human. book_table_click is useful. btn_12 is not. Consent and privacy still apply — hospitality is not an excuse for a tag soup.

Connect Search Console. Know which dishes and locations people find. A live HTML menu gives you something to rank and something to measure.

Check the booking path on mobile in the real report, not only in preview. If the click never fires, you will argue with marketing for months.

Good day-one analytics is boring and true. You can get fancy after the first month of honest numbers.

Which events matter on a restaurant site?: Menu views, allergen filter use, booking clicks, enquiry submits, and outbound clicks to OpenTable or ResDiary.
Should you wait for a data team?: No. A short, named set of events at launch beats a perfect taxonomy that never ships.