From paying for its own name to local discovery and private events.
The account we inherited was spending most of its budget advertising the restaurant's own name to people already searching for it. That budget now works the demand that was going unanswered: dine-in discovery on Google Maps, waterfront restaurant searches, private events, and catering.
Proof box
Published July 22, 2026. Updated August 3, 2026.
| Client type | Waterfront restaurant and bar, Embarcadero, San Francisco |
|---|---|
| Objective | Stop paying for branded demand; grow local dine-in discovery and build a private event inquiry pipeline |
| Channels | Google Search, Google Business Profile, Maps |
| Measurement period | May 2026 foot-traffic reporting plus 2025 to 2026 Maps/private-event operation |
| Primary outcome | 681 incremental confirmed restaurant visits in May 2026 on a $610 foot-traffic budget, plus 5 to 12 private event inquiries per month |
| Modeled visit value | Roughly $54,991 in modeled dine-in value from May confirmed restaurant visits, about 90x compared with the foot-traffic budget |
| Pipeline | $14,000 to $22,000 in monthly booked-event pipeline at roughly 40% close |
| Maps visibility | Holiday-window Maps views up 70% year over year; May 2026 Google Business Profile directions reached 5,035 |
| Budget context | A single booked event covers the monthly investment |
| Attribution status | Confirmed restaurant visits are attributed to Google advertising. Inquiries are tracked to form submissions; event values and close rates come from the venue's own booking records; estimates are labeled. |
Starting condition
In one 2024 month the account bought more than 735 clicks on the restaurant's own name for under a dollar each. Those guests were already coming. Brand clicks were driven to roughly zero by late 2025 and the budget reassigned to demand the restaurant was not capturing: people opening Google Maps, comparing nearby waterfront restaurants, and deciding where to dine or host a group.
The work
Private event and catering campaigns built around the venue's real capacity, paired with a foot-traffic program that made everyday dining demand measurable. In May 2026, the foot-traffic budget was $610 and Google Ads reported 681 confirmed restaurant visits attributed to ad interactions; that is the dine-in proof layer underneath the larger Maps and event story.
Holiday windows get their own attention: Maps views in the seasonal window rose 70% year over year, which matters because so much dine-in discovery starts with a map result, a logo, photos, directions, and a quick brand read.
Deliberately excluded: continued spend on branded terms, and inflated pipeline math. Close rates and event values come from the venue's own records, not from industry averages.
Methodology and limits
Confirmed restaurant visits are visits attributed to Google advertising. The May visit-value estimate multiplies 681 confirmed restaurant visits by a 95% attribution assumption and the venue's $85 average check, then compares that modeled value with the $610 foot-traffic budget. Inquiries are counted at form submission and cross-checked with the venue's event platform. Pipeline multiplies inquiries by the venue's observed average event value and close rate; it is a forecast, not booked revenue, and is labeled that way. Maps views are visibility, not seated covers, so they are used to support the dine-in discovery story rather than replace conversion reporting.
What the spend produced
"Right people, right message, right time."Karen Wong, Owner, Harborview Restaurant & Bar