TablePort Ads · Early accessFill quiet nights with
Meta ads you control.

Run Facebook and Instagram ads from your own Meta ad account, inside rules you set in TablePort. Lock a monthly cap Meta enforces itself, approve every ad before it goes live, and compare Meta spend against the bookings that actually sat down.

Early access, switched on per restaurant by our team. Your own Meta ad account. You pay Meta directly. No cut of ad spend.

A host leads arriving guests in coats between full tables, menus in hand.
19:05Midweek dinner filling up

The problem

Most restaurant ad spend disappears into a black box.

Agencies and black-box reporting

You hand over account access, pay retainers or percentage cuts of spend, and get a monthly deck of reach and impressions. It still cannot tell you how many guests actually sat down.

Budget burned on full Fridays

Generic ad setups do not know what your booking diary looks like. They keep spending on nights you were going to fill anyway, or run past what you meant to commit.

Guest data shared without asking

Tracking pixels that load on arrival and exported email lists uploaded without separate consent leave the restaurant carrying UK GDPR and PECR risk.

How it works

Four steps from setup to the first live campaign.

Nothing can spend until every readiness check is green, Meta confirms your spending limit, and a person approves the campaign.

  1. 01Early access

    Switch it on with our team

    TablePort Ads is enabled per restaurant. We complete legal and ownership checks together, and you declare your business size for UK healthier-food (HFSS) rules.

  2. 02Your own account

    Connect Meta and lock your cap

    Connect the Meta ad account, pixel and Business Manager your restaurant owns and pays directly. Save your monthly cap and we mirror it to Meta as the account spending limit.

  3. 03Human approval

    Draft, check and approve

    Build a campaign with a real, unaltered photo of what you serve. The creative check flags text limits, unapproved offers and HFSS rules before a person approves it.

  4. 04Paused first

    Deliver only inside your rules

    Approved campaigns publish to Meta paused first. They go live only while every readiness check passes, never on blocked weekdays, and pause when a service reaches your fill threshold.

Control by design

Rules Meta has to obey, not polite suggestions.

Your settings in TablePort act as your written instructions. Campaigns start paused, follow your blocked days and fill limits, and log every decision with who made it.

  • Your own Meta ad account

    You pay Meta directly on your own card. TablePort never holds ad money and never takes a cut of spend.

  • Monthly cap enforced by Meta

    Your cap is set as Meta's account spending limit and read back to verify remaining room before anything delivers.

  • Days never to promote and fill limits

    Block busy weekdays in your venue's local time, and pause promotion once forecast bookings reach your threshold.

  • Approval first, slow pacing later

    A person approves every action for at least the first 60 days. Pacing spreads spend evenly; later automatic adjustments move in small daily steps inside your cap.

  • Emergency stop and decision log

    One emergency stop halts every published campaign on Meta at once. Every approval, publish, budget change and pause is logged.

Proof you can trust

Meta's numbers beside what happened in your dining room.

TablePort shows two sources side by side and never blends them: what Meta reports for delivery, and which bookings through the ad's link actually came in and paid a bill.

Meta delivery, synced nightly
Spend, impressions, reach, link clicks, click rate and cost per click, straight from Meta Insights, with daily charts and per-campaign pages.
TablePort outcomes, from your reservation book
Bookings made through each ad's link, covers, cost per booking, show rate, net bill revenue of seated ad bookings and return on ad spend.
Aggregates only, never individual guests
Every funnel stage, from saw the ad to spent at the table, reports totals only. No guest is ever singled out in ad performance reports.

Ad previews and creative check

See every placement before a guest does.

Preview how your real dish photo, headline and Book now button sit across Facebook feed, Instagram feed, Instagram story and Facebook story before you press approve.

Checked before every approval

  • Real, unaltered photo of what your kitchen actually serves
  • Headline, main text and call-to-action limits checked before approval
  • Any offer in an ad must use wording from your approved offers list
  • Alcohol stays out of ads unless you switch it on; every ad targets adults 18 and over
  • HFSS-safe creative confirmation required for larger groups (250+ staff or large franchises)
  • Pause, resume or archive any campaign from TablePort
Osteria MaraSponsored ·

Chargrilled bavette and seasonal plates straight off the pass. Book a midweek dinner table in Soho.

Freshly plated dishes at the kitchen pass in an illustrative Meta ad preview
osteriamara.co.ukQuiet tables, Tuesday to ThursdayDirect booking, no fees
Book now

Privacy and consent

Built for UK GDPR and PECR, not bolted on after.

Guests decide on your booking site whether advertising cookies load and whether their booking details may be used for ads. Default is deny, and every sent event is checked against the consent record.

  • Consent banner off by default

    Ad cookies and Meta's pixel stay off until a guest says yes on your booking site. Reject and Accept appear at the same size and weight, and Global Privacy Control is respected automatically.

  • Separate unticked box for guest-list ads

    Using booking details for ad audiences is a separate, unticked choice. Custom audiences include only opted-in guests who booked in the last 13 months, and only when at least 100 guests qualify.

  • SHA-256 hashing and strict allowlists

    Nothing about a guest reaches Meta without that guest's consent. Contact details are hashed with SHA-256 before sending, and only allowlisted fields can leave TablePort: allergies, dietary notes, guest notes and order lines are never sent.

  • 24-hour removal, 90-day deletion and nightly audits

    Withdrawals or erasure requests purge unsent events and queue removal from your ad audience within 24 hours. Stored ad data is deleted after 90 days, and a nightly audit pauses campaigns automatically if any sent row fails re-check.

Straight answers

What TablePort Ads is not.

Before you ask us to switch it on, here is what we will not promise and what we do not do.

  • No guaranteed bookings or returns

    Paid ads depend on your neighbourhood, your dishes, your photography and the night of the week. We never promise seated covers or guaranteed return on ad spend.

  • No cut of your ad spend

    You pay Meta directly from your own ad account. TablePort never holds your media budget and never takes a percentage of what you spend.

  • No automatic spending before you are ready

    Early access is switched on per restaurant by our team after legal and ownership checks. Accounts start paused, and campaigns publish paused until every check is done.

  • Meta first, not unproven promises

    TablePort Ads runs on Facebook and Instagram through Meta today. We only describe what is built and live in the console.

Questions, answered

What owners ask before switching ads on.

Want to check how early access works for your site? Talk to us.

TablePort Ads is in early access and is switched on per restaurant by our team. Book a walkthrough or contact us to ask for early access, and we will guide you through the readiness checklist.

Your restaurant uses its own Meta ad account and pays Meta directly from your own card. TablePort only holds partner access to publish and sync within your rules. TablePort never holds your ad money and takes no cut of your ad spend.

Your monthly cap in TablePort is mirrored to Meta as your account spending limit, and TablePort reads back the remaining room on Meta before campaigns can deliver. You can also stop everything immediately with the emergency stop.

Yes. Every campaign draft passes a creative check, is approved by a person, and publishes to Meta paused first. For at least the first 60 days after connecting your account, a person approves every action.

Performance keeps two sources side by side and never blends them: Meta delivery numbers synced nightly (spend, impressions, reach, link clicks, click rate and cost per click) and TablePort outcomes (bookings through the ad's link, covers, show rate, net bills of seated guests and return on ad spend). Reports show aggregate counts only, with no guest identified.

Ad cookies and Meta's pixel stay off on your booking site until a guest agrees, with Global Privacy Control respected automatically. Letting your restaurant include a guest in an ad audience uses a separate unticked tickbox. Contact details are hashed with SHA-256 before sending, only allowlisted fields can leave TablePort, withdrawals or erasures remove guests within 24 hours, and stored ad data is deleted after 90 days.

Yes. Choose any weekdays to never promote, using your venue's local date, and set a forecast fill threshold so TablePort pauses promotion for a service once bookings reach that level.

No. Ad performance depends on your neighbourhood, your photos, your offer and the night of the week. TablePort gives you strict spending limits, human approval and honest reporting, never guaranteed covers or returns.
A host at the stand checking bookings as a group arrives, the dining room full behind them.
19:30Quiet Tuesday, booked direct

Early access

Run Meta ads on your own
account, inside your own rules.

TablePort Ads is switched on per restaurant by our team. Book a walkthrough or get in touch to ask for early access.