Case Study 04 · The Attribution Story
Premium steakhouse group · Dublin 2 · name withheld
What was recorded. What it does not prove.
OpenTable recorded 3,699 network covers. Google Business Profile recorded visibility and actions. These are separate datasets, not proof that every booking was caused by marketing.
3,699
Network covers
Recorded by OpenTable; not proof of bookings caused by Moolah
Source · OpenTable
20pt
Gap versus local market
Venue +7% covers, Dublin 2 market −13%
Source · OpenTable
70.8K
Profile actions
Website clicks, directions, calls and reservation taps; not bookings
Source · Google Business Profile Insights
In brief
- 3,699 network covers recorded by OpenTable; not proof of bookings caused by Moolah.
- The venue grew 7% while the local market fell 13% — a 20-point gap.
- Search and booking data are kept as separate, parallel evidence.
The situation
The venue grew covers while its local market declined. OpenTable and Google records show different parts of the picture, not a single booking journey.
What the period showed
Google visibility data and OpenTable booking data are separate records. No conversion from profile actions to covers or share of growth is claimed.
Reading the Evidence
Recorded outcomes. Not a claim of sole credit.
This city-centre steakhouse grew covers by 7% while its local market fell 13%. The 20-percentage-point gap is recorded in OpenTable's venue and market data.
Food, service, reputation and market conditions also affect bookings. The figures below show what the platforms recorded during the engagement, without assigning a financial value or a share of total growth to Moolah.
The Evidence Boundaries
Three distinctions. No assumed conversions.
Recorded · OpenTable
Platform-recorded network covers
3,699
Network covers · OpenTable
OpenTable recorded these covers in its network channel. A recorded booking channel is not a measurement of bookings caused by Moolah.
Recorded · Google Business Profile
Visibility and profile actions
70.8K
Profile actions · Google Business Profile Insights
The profile recorded 357K impressions and 70.8K actions. Actions include website clicks, direction requests, calls and reservation taps. They are not all bookings or visits.
Not claimed
A share of the restaurant's growth
Not assigned
No share of growth assigned
These datasets do not isolate the contribution of marketing from the kitchen, the floor team, the brand or wider market conditions. No share of growth is assigned to Moolah.
Separate Platform Records
Visibility, actions and covers. Not one tracked journey.
Profile Impressions
357K
Google Business Profile Insights
Recorded appearances in Google Search or Maps over the tracked year.
Profile Actions
70.8K
Google Business Profile Insights
Website clicks, direction requests, calls and reservation taps recorded by the profile.
Network Covers
3,699
OpenTable
Network covers recorded by OpenTable; not a conversion total derived from Business Profile actions.
Confidentiality and attribution
Client names are withheld. Every figure comes from the client's own third-party platform data, and its source is named.
Search, local profile and booking-platform figures are recorded by separate systems and are presented here as parallel indicators over the same period. Where a movement is not directly traceable to a single guest journey, it is described as correlation and commercial context rather than proven causation.
Strategy & analysis by Alex Opsenica, Moolah Media
The method behind this engagement
Next case study
How a restaurant search actually becomes a booking.Keep reading
Other case studies from the same engagements.
Chef-led landmark restaurant · Dublin city centre · name withheld
Entering an occupied market and ranking ahead of it.
From no non-branded visibility to a #7 Google local results position on Dublin's most contested restaurant discovery term.
View case studyPremium steakhouse group · Dublin 2 · name withheld
Building local search infrastructure from the ground up.
Fifteen months of local search infrastructure: Domain Authority 33 to 47, linking domains 104 to 197, 83% map pack coverage.
View case studyChef-led landmark restaurant · Dublin city centre · name withheld
When the local market fell, this restaurant grew covers.
Covers grew 33% year on year while a 75-venue OpenTable benchmark for the same area fell 9% — a 42 percentage-point spread.
View case studyFree Restaurant Visibility Audit
What could better visibility mean for your restaurant?
Results shown are historical examples from specific restaurant engagements. Outcomes vary by market, competition, starting position and implementation.