Facebook & Instagram ads for restaurants

Here is how it usually goes. The post is doing alright, so the owner hits the blue Boost button, throws fifty dollars at it, and Facebook reports a few thousand "people reached". Feels productive. Then the week ends and nobody can point to a single booking that came from it. The money went to likes from people who will never set foot in the place.

Boosting is the trap because it is easy and it shows you a big number. But it skips everything that makes ads work: a real objective, a tight location, the right audience, a tracked action, and creative built to test. Without those, you are paying Meta to show your post to whoever is cheapest to reach, which is rarely a hungry local near your door.

The flip side is that Meta is one of the few places you can fill a specific quiet Tuesday this week. The targeting and the speed are genuinely powerful. They just have to be pointed at a booking, not a vanity metric.

We don't buy reach. We buy covers, and we can prove which campaign, which audience and which ad delivered them.

Australian cities are spread out, so radius targeting matters more here than in dense overseas markets. A diner will happily cross a few suburbs in Brisbane or Perth but not the whole metro, so we set the radius to the real catchment your venue draws from, and we lean harder on it for venues outside the tight inner-city grids.

Timing is everything for venue ads. We push offers ahead of the moments that fill rooms here: long weekends, Melbourne Cup, footy finals, end-of-year functions from late October, and Valentine's and Mother's Day for the venues they suit. We also use ads to defend the quiet stretches, like the long February lull, when a well-placed midweek offer earns its keep.

And we keep the spend honest. Any ad involving alcohol follows Meta's restrictions and Australian responsible-service rules, and we keep your ad account and customer data in your own hands so nothing is locked to us. You can see exactly what went to Meta and what went to running the work.

Want the mechanics? Module 10 of the Playbook covers paid ads for venues end to end, from audiences to creative to reading the numbers.

Most venue ad accounts are a mess of half-finished boosts with no structure underneath them. That is why the spend never adds up. Before we run anything, we set the account up the way it should have been from the start.

That means a Business Manager that you own, with your page, your ad account, your pixel and your payment method all sitting under it. Not ours. If we part ways, you keep the lot, including the history and the audiences you have built. We have seen too many owners locked out of their own data because an agency built everything inside their own account. We do the opposite.

Inside the account, campaigns are kept clean and separate by job. One campaign chasing awareness should never share a budget with one chasing bookings, because Meta will quietly feed the cheaper-to-serve one and starve the other. We keep budgets, audiences and objectives apart so each can be read on its own and turned up or down without dragging the rest with it. We also set conversion events properly in Events Manager and rank them, so Meta knows a booked table is worth more than a page view. Skip that and the system optimises toward whatever is easy, which is almost never a cover.

The Meta pixel is a small piece of code on your site that tells Meta what people do after they click: view the menu, start a booking, finish one. That signal is what lets the system go and find more people like the ones who actually booked. Without it, you are guessing.

The problem is that browser tracking has been quietly breaking for years. Apple's privacy changes, ad blockers and cookie limits mean the pixel alone now misses a big share of what really happens. That is where the Conversions API comes in. It sends the same events to Meta server to server, from your booking system or website backend, so a booking still gets counted even when the browser signal is lost. Running the pixel and the Conversions API together is the difference between Meta seeing most of your results and seeing half of them.

We wire both up before launch, test that a real booking fires a real event, and make sure the data deduplicates so one booking is not counted twice. Then we set the conversion as the thing campaigns optimise toward. Get this layer right and everything downstream, the targeting, the scaling, the reporting, actually works. Get it wrong and you are flying blind no matter how good the ads look.

If an agency wants to spend your money before the pixel and Conversions API are firing on a test booking, that is the moment to stop.

The creative that works for venues is almost never the glossy, over-produced kind. It is a real phone video of the pasta being finished, the room filling up on a Friday, the bartender making the drink people come back for. It looks like the feed it sits in, so people watch it instead of scrolling past, and it looks like you, so the diner who turns up gets what they were sold.

We shape this from your own content. A short list of the shots that sell, a simple way to film them during service, and then we cut, caption and script them into ads. Captions matter because most of this is watched on mute. The first second matters most, because that is all you get before the thumb moves.

Then we test. Three or four angles against each other: the dish, the room, the offer, the regular's review. We keep what produces bookings, kill what does not, and refresh the winners before they tire, because the same ad shown too long to the same people stops working. This is ongoing, not a one-off shoot.