Dacha case study
Turning private dining demand into a steady event pipeline.
Dacha already had the ingredients: restaurant, catering, cocktail classes, and corporate-event potential. The work was to route search demand toward the higher-margin side of the business and separate private-event demand from ordinary dining traffic.
The numbers at a glance
Proof box.
Published August 3, 2026. Measurement window: January through May 2026, with June context included.
| Client type | Eastern European restaurant, catering program, and cocktail-class venue, San Francisco |
|---|---|
| Objective | Grow private-event and corporate-dining inquiries without confusing them with normal foot traffic |
| Channels | Google Search, Google Business Profile, local SEO, private-event page positioning |
| Measurement period | January through May 2026 primary window; June used as seasonality/context check |
| Primary outcome | 18 to 23 tracked private-event inquiries per month from January through May 2026 |
| Peak pipeline | Roughly $25,000 to $29,000 in expected private-event pipeline in peak months |
| Local SEO layer | Google Business Profile visibility supported local discovery: 100,755 views and 1,177 directions in May 2026 |
| Blended return | Roughly 20x to 34x monthly modeled return across private events, visits, reservations, and calls during the same window |
| Attribution status | Private-event inquiries are tracked form submissions. Confirmed restaurant visits are attributed to Google advertising. Business Profile views and directions are local-discovery actions. Pipeline uses Dacha's average event value and modeled close-rate assumptions, so it is expected value rather than booked revenue. |
Starting condition
Dacha's marketing opportunity was not just more restaurant traffic. The healthier growth path was event demand: private dining, catering, corporate gatherings, and classes that can carry stronger margins than ordinary service. The account needed a system that valued the right lead, not the loudest vanity metric.
The work
Campaigns and local-search signals were tuned around private-event intent. Business Profile upkeep kept the brand visible in the map moments around dining, directions, calls, and event research. The reporting split event inquiries from confirmed restaurant visits and reservations, then translated private-event demand into expected pipeline using Dacha's own average event value.
Deliberately excluded: counting impressions, viral reach, or generic traffic as the win. The business question was whether the marketing created right-fit private-event demand that an operator could actually pursue.
Methodology and limits
Private-event inquiries are counted at form submission. Confirmed restaurant visits are attributed to Google advertising. Google Business Profile views and directions show local discovery, not booked-event revenue. Expected pipeline multiplies inquiries by the client's average event value and modeled close-rate assumptions. That means the figures are pipeline estimates, not booked revenue. June dropped to 9 tracked private-event inquiries and roughly 14x modeled return, so the public claim is intentionally limited to the stronger January through May window.
Results
What the spend produced.
All case studies Private events program Ask about the methodology