Home/Resources

AdsAugust 202610 min read

Meta Ads for a restaurant: a guide to filling your tables

Objectives, campaign / ad set / ad structure, local targeting, Pixel and Conversions API, budget: launch your restaurant Meta Ads with a method.

A martini and a vintage phone in amber light

Running Meta Ads (Facebook and Instagram) for a restaurant means paying to appear in front of people near your venue, with one precise goal: filling tables. The difficulty is in the details: structuring the account properly, choosing the right objective, measuring a booking that sometimes happens on another website, and spending with a method rather than a guess.

This guide explains how to launch your first Meta Ads campaigns for a restaurant: objectives, campaign / ad set / ad structure, geographic targeting, audiences, creatives, the Meta Pixel and the Conversions API, budget, and common mistakes. Meta's interface changes often, so we describe the logic and the stable settings, and flag what may differ as of writing (November 2026).

Meta Ads campaign objective and account structure for a restaurant

The objective is chosen at campaign level and drives everything else: Meta optimizes delivery for what you ask it to achieve. It is locked once the campaign is created, so changing it means building a new campaign.

Meta has consolidated its objectives into a shorter list (Awareness, Traffic, Engagement, Leads, App promotion, Sales). Depending on your account, you may still see the older list (Awareness, Consideration, Conversions): Meta's help pages say the rollout is gradual. The logic is the same.

For a restaurant, the choice depends on what you want:

  • Online bookings: choose the objective focused on results on your website (Sales or Conversions depending on the screen), with a confirmed booking as the optimization event. This is the best choice as soon as your tracking works.
  • Local visibility (opening, new menu, new venue): the Awareness objective reaches as many people as possible in your area. Keep it for launch phases, because it does not optimize for bookings.
  • Visits to your booking page without reliable tracking: the Traffic objective sends clicks or page views. It is a plan B if bookings cannot be measured, but it also attracts curious visitors who never book.
  • Private-event or group enquiries: the Leads objective, with a form or a messaging conversation, suits requests that are handled through discussion.
Worth remembering: an objective lower in the funnel (booking) beats a click objective, provided Meta receives enough signals. Without booking tracking, a simpler objective is better than misleading numbers.

Account structure: campaign, ad set, ad. Meta Ads Manager works on three levels, described in Meta's official help:

  • The campaign: you choose the objective (and the buying type, usually auction).
  • The ad set: it defines the audience, placements (Instagram, Facebook, Stories, Reels…), budget and schedule. All ads in the same ad set share these settings.
  • The ad: the creative (image, video, text, button), plus the Facebook Page and Instagram account shown as the advertiser.

For a single restaurant, two campaigns are enough:

  • A "Bookings" campaign, with one ad set for your main catchment area, and two or three different ads to compare.
  • An "Events or key moments" campaign (New Year's Eve, Mother's Day, summer menu) launched only when you need it, with its own budget.

Name everything clearly (for example "Booking | Neighbourhood | Summer menu | Reels"). Multiplying ad sets with small budgets is a common mistake: each ad set needs enough delivery for Meta to learn.

Geographic targeting and audiences for restaurant Meta Ads

Geographic targeting.

For a restaurant, geographic targeting matters more than most other settings. At ad set level, you define a location: a city, a neighbourhood, or an address with a radius.

As of writing, Meta's default location option is "People living in or recently in this location". It includes people whose home or most recent location falls in the area, including people passing through. That can suit a tourist or office-district address, but less so a neighbourhood restaurant aimed at residents. Check which options your screen offers.

A few practical rules:

  • Draw a realistic area. Drop a pin on your address and set a radius consistent with your customers (on foot, by car, by public transport).
  • The radius has limits. The minimum and maximum vary by location type, it does not cross country borders, and it is not available on postal codes.
  • If you target residents, pick the residents-only option rather than the default, when your screen offers it.

Audiences. Once the area is set, you choose who sees your ads. Three approaches coexist.

Broad audience. You specify almost nothing beyond the area and minimum age. For a restaurant with a wide clientele, this is often a good starting point: Meta looks for people who respond. It assumes your conversion tracking works.

Interest-based audience. Useful for testing a specific concept (brunch, natural wine), but interests remain approximations.

Custom audiences. These are the most valuable for a restaurant, because they rely on your own data:

  • visitors to your website or booking page (via the Pixel);
  • people who engaged with your Instagram account or Page;
  • your customer list, imported with consent (see our article on email marketing and GDPR).

You can use these audiences to target (follow up with visitors who did not book) but also to exclude: there is no point paying to show a prospecting ad to your regulars.

Creatives that make people want to book: formats, copy and call to action

In a fast-scrolling feed, the creative makes the difference. What generally works, to be tested on your own venue:

  • Real content: your dishes, your room, your team, shot at your place. Stock photos are easy to spot.
  • Several formats of the same idea: vertical for Stories and Reels, square or vertical for the feed.
  • Videos that show the dish or the atmosphere in the first seconds, with subtitles.
  • Concrete copy: the neighbourhood, the cuisine, what makes your table different, and a clear call to action ("Book a table").
  • A consistent landing page: customers must find the same offer and be able to book in two or three taps on mobile. A beautiful ad leading to an unreadable PDF menu wastes the budget.

Test one variable at a time (visual, hook, format).

Meta Pixel and Conversions API: measuring bookings

Without measurement, you will not know whether advertising fills your tables. Meta offers two channels to tell it what happens on your site:

  • The Meta Pixel, code running in your visitors' browser;
  • The Conversions API, which sends events from a server (yours or a partner's).

Meta recommends using both together (a "redundant setup"), because the browser can lose events (cookie refusals, blockers, navigation across several sites). You must then deduplicate: the same event must carry the same identifier on both sides (eventID browser-side, event_id server-side, with the same event name). Meta then discards the duplicate received within 48 hours. Events sent through only one channel need no deduplication.

For a restaurant, here is a setup method:

  • Define the event that counts: the confirmed booking, not merely a page visit. Pick the closest standard event in Meta or create a custom event.
  • Check your booking engine. If bookings happen on a different domain from your site, the site's Pixel does not see the confirmation. The event must be triggered from the confirmation page or from the server. Ask your vendor, as this varies by tool.
  • Test in Events Manager: the Test Events tool (Events Manager > Test Events) shows events arriving before you spend anything.
  • Respect consent. In France, placing advertising trackers requires consent. The CNIL requires that refusing be as easy as accepting, so your banner must offer a refusal at the same level as acceptance.

To connect click, booking and actual bill, also read our guide on the ROI of restaurant advertising.

What Meta Ads budget for a restaurant: a calculation method

We will not give a universal budget: there is none. Here is a method for setting yours.

  1. Start from the value of a booking. What is the average spend per cover, the average covers per table, and your margin? That tells you what a booking is worth to you.
  2. Set an acceptable cost per booking: a fraction of that value you are willing to invest to win it.
  3. Set the booking target for the period (for example 4 weeks), based on the tables to fill.
  4. Multiply: budget for the period = target bookings × acceptable cost per booking. Then divide by the number of days for a daily budget.
Fictional example: a restaurant whose booking is worth on average €120 in revenue accepts paying up to €12 to win it. To aim for 50 bookings in 4 weeks, the budget is 50 × 12 = €600, or about €21 per day. These figures illustrate the calculation: they are neither a real result nor a recommendation.

Three points from Meta's help:

  • A daily budget is an average: on some days Meta may spend up to 25% more, with weekly spend capped at seven times the daily budget. A lifetime budget is another option.
  • Each ad set has a minimum budget, which depends on your account.
  • The learning phase ends when the ad set reaches about 50 optimization events after the last significant edit. If your restaurant does not generate that volume of bookings, Meta will flag "learning limited". Suggested fixes: a broader audience, a higher budget, or a more frequent optimization event. Do not keep changing audience, creative and budget: each significant change can restart learning.

Common Meta Ads mistakes for restaurants

  • Not measuring the booking, and judging on likes or cost per click.
  • An area too wide or too narrow, inconsistent with your real customers.
  • Too many ad sets, too little budget: learning never happens.
  • Sending the ad to a slow or confusing page, or a PDF menu.
  • Double counting bookings from Meta and Google, each platform claiming the credit.
  • Neglecting your local listing: an ad makes people search your name on Google, where a polished listing should be waiting (Google Business Profile).

Meta Ads for restaurants: frequently asked questions

Which Meta Ads objective should I choose to fill my restaurant?

If your online booking is properly tracked, choose the results-focused objective on your website (Sales or Conversions depending on the screen) with the booking as the event. Otherwise, Traffic is a plan B. For a launch, Awareness reaches your area.

Do I need to install the Meta Pixel and the Conversions API?

Meta recommends using both together, with deduplication through an event ID. The Pixel alone can lose events. In every case, test your events in Events Manager and respect consent.

How much should I spend per day on Facebook and Instagram ads?

There is no universal amount. Start from the value of a booking, set an acceptable cost per booking, then multiply by the number of bookings you are aiming for. Adjust afterwards based on the results you actually measure.

How do I target only the residents of my neighbourhood?

In the ad set, define a location with a pin and a radius, then check the location option: the default includes people who were recently in the area. Choose the option suited to residents if that is your target.

Need help with your restaurant Meta Ads campaigns?

Objective, area, audiences, tracking, consent: the settings interact quickly. māhie supports 90+ restaurant and hospitality venues, and Ads campaigns are part of our daily work. Concretely, we can:

  • define the media strategy and the right budget on the right platform;
  • create the ads, in formats adapted to each platform;
  • run launches and events: openings, evenings, seasons;
  • set up retargeting to bring back those who hesitated;
  • track bookings to connect every euro to covers, with clear reporting.

Discover our Ads services, or contact māhie and we will look at your situation together.

Corentin
CorentinFounder of māhie