The single highest-ROAS dollar in your restaurant marketing budget is the dollar you spend retargeting a person who has already eaten at your restaurant or already handed you their email address. Cold prospecting on Meta and Google in 2026 returns somewhere between 1.0 and 2.5x for an average independent. Retargeting returns 3 to 7x, and well-run accounts hit 8 to 12x. The gap is not subtle. It is the difference between paid ads being a tax you pay to grow and paid ads being a profit center.
Most restaurants never run it. Or they ran it once, set it up wrong, never came back, and decided “Facebook ads do not work.” This is the playbook that actually works for restaurant operators in 2026, post-iOS 14, post-cookie-deprecation, in a world where your first-party customer data is the asset that compounds. It covers the four audience types worth running, how to build them in Meta and Google, how to define a lapsed customer from your own POS, what creative wins, what frequency caps to set, and how to launch in 30 days.
One disclosure before we start, because it changes how you should read the rest. The Restaurant Velocity app does not run your Meta or Google ads. It automates the Google Business Profile side of your marketing, the local discovery layer that quietly feeds the first-party list this entire retargeting playbook depends on. So read this as the operator guide we would hand a marketer, built from restaurant ad accounts we have analyzed and current 2026 platform benchmarks, not as a pitch.
Why Restaurant Retargeting Has the Highest ROAS in Your Whole Marketing Stack
The math is simple. A cold prospect on Meta has never heard of you, never tasted your food, and has roughly a 0.3 to 1.2% chance of converting on any given ad impression. They need three to seven touches before they walk in. The cost adds up. Blended acquisition cost for cold paid traffic in casual dining sits between $25 and $80 per first-time customer, depending on metro and concept.
A retargeting prospect already knows you. They visited your site, opened your email, watched a Reel, or ate in your dining room. Their conversion rate runs 4 to 12x that of a cold prospect. Their cost per click is often lower because the ad’s relevance score is higher (Meta and Google reward ads that earn strong engagement from the audience they are shown to). And their average order value is higher because they convert with more confidence.
So why do most restaurants skip it? Three reasons. First, the setup feels intimidating: pixels, Conversions API, customer list uploads, hashed data, audience overlap. Second, owners hear “Facebook ads do not work” from peers who never built a retargeting layer at all. Third, the email list and POS database, the foundation of the whole thing, are usually ignored or scattered across systems. None of those are real obstacles. They are training problems. Fix them once and you own an asset that compounds for years.
The gap holds up in the 2026 benchmarks. Custom audiences of past purchasers, site visitors, and video viewers typically return 5 to 10x versus cold traffic, and a good restaurant ROAS on Facebook now sits in the 5 to 8x range with the top quartile above 7x (2026 industry benchmark data). Restaurant ROAS has compressed roughly 20 to 30% since 2020 because of iOS attrition and rising CPMs, which is exactly why the warm-audience premium matters more now, not less.
The Viability Threshold: When You Are Too Small to Retarget Profitably
Here is the part almost no retargeting guide will tell you, because most of them are written by people who want you spending on ads today. Below a certain audience size, paid retargeting does not work, and running it anyway just donates money to Meta. The reason is structural. Meta’s delivery system needs roughly 1,000 matched users to stabilize; under that, it cannot control frequency, CPMs inflate, and your data comes back too thin to read.

Work back from the matched size. A blended email-and-phone list matches at about 60% in 2026, so an audience of 1,000 matched users needs roughly 1,700 reachable customers behind it. That is the real floor. If your combined POS, email, reservation, and online-order lists add up to fewer than about 800 reachable people, you are not a retargeting candidate yet, and no amount of clever creative changes that.
The contrarian move for a small independent is to spend zero on paid retargeting and instead compound the list. Every net-new email captured, every new reservation, every Google Profile visitor who becomes a follower moves you toward the threshold. This is the honest reason local discovery matters before ads do: it fills the top of the funnel that retargeting later monetizes. If you are under the line, put the $500 you were about to burn on a 400-person Meta audience into review velocity, profile freshness, and list capture instead. Start your 14-day free trial if you want that discovery layer running on autopilot while the list grows to size.
The Four Retargeting Audience Types Every Restaurant Should Run

Once you clear the threshold, understand the audience taxonomy before touching a budget. Every retargeting ad in 2026 falls into one of these four categories, and a mature restaurant ad account runs all four.
1. Pixel-Based Audiences (Web Visitors)
Built from your Meta Pixel and Google Ads tag. These capture anyone who visited your website, viewed your menu, started an online order, or landed on your reservations page. The windows we use most: 7 days (high intent, recent), 30 days (most of the budget), and 180 days (long-tail re-engagement).
Pixel audiences are the smallest of the four for most restaurants. An independent with 5,000 to 15,000 monthly site visitors rarely sees a 30-day pixel audience exceed 8,000 matched users on Meta after iOS attrition. That is fine. Pixel audiences are about intent, not size.
2. List-Based Audiences (Customer Match)
Built from your hashed email and phone list, uploaded to Meta Custom Audiences and Google Customer Match. This is the workhorse for restaurants. A 5,000-email list at 65% match gives you a 3,250-person Custom Audience you can retarget for under $20 a day and consistently pull 5 to 8x ROAS.
Match rates in 2026: 50 to 75% for email, 30 to 60% for phone. The variance comes from list age (older lists carry more dead emails), source (opt-in forms match higher than purchase emails because people used a real address), and platform (Meta tends to match higher than Google).
3. Engagement Audiences (Social Profile Activity)
Built from people who interacted with your Instagram or Facebook profile in the last 365 days. They liked a post, watched a Reel, sent a DM, saved your menu, or visited your profile. Undervalued, because most operators do not realize how large it gets with consistent posting. A restaurant with an active Instagram (4 to 6 posts per week, decent food photography) can build a 50,000-plus engagement audience in 12 months.
Engagement audiences are cheap to retarget because the relevance score is high. People who already engaged with your brand on social will engage with your ad on social. CPM drops 20 to 40% versus pixel.
4. Video-Viewer Audiences
Built from people who watched a percentage of your video content. We use 50% video views in the last 90 days as the threshold. This is the cheapest audience to build. A single Reel that hits 100,000 views can populate a 50,000-plus video-viewer audience in a week, even on small budgets.
Video viewers are mid-intent. Interested enough to watch, not so interested they visited your site. The play is to escalate them: a 50% video viewer who has not converted in 30 days gets the offer ad.
Building Your First-Party Data Foundation
Retargeting starts before you ever open Meta Ads Manager. It starts with the data you hold on your customers. In 2026, with cookies sunset on Chrome and iOS 14-plus stripping deterministic attribution, first-party data is the asset that compounds. Get this right and your program is alive in five years. Skip it and you rebuild audiences every six months.
The four data sources that matter for restaurants:
- POS customer data: Toast, Square for Restaurants, Lightspeed, Clover, and TouchBistro all capture customer email and phone at checkout when set up correctly. Most restaurants have this turned off or under-used. Turning it on and exporting weekly produces the largest first-party list you will ever build.
- Email platform: Klaviyo, Mailchimp, Constant Contact, or your loyalty platform’s built-in tool. This is your opted-in marketing list. Sync it to Meta Custom Audiences daily through a native integration or a weekly CSV upload.
- Reservation system: OpenTable, Resy, Tock, SevenRooms. Rich profiles with visit count, last visit date, party size. Export and segment.
- Online ordering platform: Toast Online Ordering, ChowNow, Olo, Square Online. Online orderers hand you full contact info every time. High-LTV segment.
Your job is to consolidate. Pick one customer database (your email platform is usually the right home), import the others, deduplicate by email, and treat that file as the source of truth for retargeting uploads. Re-sync to Meta and Google every 7 to 14 days. Restaurant email list building walks through the capture mechanics in depth.
Meta Custom Audiences for Restaurants: Setup and Match Rates
Meta is the primary retargeting platform for restaurants in 2026. The volume of warm audiences (Instagram is where your customers live) and the depth of audience definitions make it the strongest single channel. Here is the setup playbook.
Step 1: Pixel + Conversions API
The Meta Pixel alone is no longer enough. Conversions API (CAPI) sends conversion events server-side, bypassing the iOS browser-level tracking restrictions. Pixel-only restaurants leak 20 to 35% of attributable conversions in the iOS share of traffic. Set up CAPI through your CMS plugin (WordPress, Shopify, Squarespace), through Stape or Zapier as middleware, or through native Toast and Square integrations where available. Aim for a match-quality score of 8.0 or higher so the algorithm has full signal to optimize on.
Step 2: Build the four pixel audiences
Inside Meta Ads Manager, build these four website Custom Audiences:
- All website visitors, last 30 days (the broad audience)
- Menu page visitors, last 30 days (mid-intent)
- Online order start (initiate checkout), last 30 days, exclude purchasers (high-intent, abandoned)
- Reservations page visitors, last 14 days, exclude bookings (high-intent, considered)
Step 3: Upload your customer list
Export from your email platform or POS. Required fields: first_name, last_name, email, phone (with country code), city, state, ZIP, country. Optional but valuable: date of birth, gender, last_order_value. Hash with SHA256 before upload (Meta does this automatically in the dashboard, but if you upload via API or CSV with hashing, double-check the format).
Upload to Audiences, Create, Custom Audience, Customer list. Wait 24 to 72 hours for the match rate to populate. Expect 50 to 75% match for email-primary lists. Below 40% match, audit list cleanliness (typos, role addresses, dead domains).
Step 4: Build engagement and video audiences
From the Audiences page: Custom Audience, Sources, Instagram account, Everyone who engaged, last 365 days. Repeat for the Facebook page. Then video views: Sources, Video, People who watched at least 50% of any video, last 90 days.
Step 5: Build lookalikes off the high-LTV slice
Lookalikes off your full customer list are weaker than lookalikes off your top 25% LTV slice. Filter to customers with 5-plus orders or above-average lifetime value, upload that as a separate Custom Audience, and create a 1% lookalike off it. This becomes your premium prospecting audience.
Operator math. A 5,000-email list at 65% match gives a 3,250-person Custom Audience. Run a 30-day campaign at $25 a day ($750 total) at 4x average frequency and you reach all 3,250 people about four times. Convert at 1.5 to 3% in-store visit rate and that is 50 to 100 visits at a $30 to $50 ticket, or $1,500 to $5,000 in tracked revenue. ROAS 2x to 6.7x. Real numbers, not theory.
Google Customer Match and Display Retargeting for Restaurants
Google is the secondary retargeting channel for most restaurants, but not the less important one. It reaches the customer on different surfaces (Search, YouTube, Display, Gmail) and at different intent moments. Run both Meta and Google for full coverage. Restaurant Google ads covers the full account architecture; this section is retargeting only.
Customer Match setup
Google requires Customer Match accounts to meet a policy threshold (good standing, history, sometimes a minimum spend). Once approved, upload your hashed list under Audience Manager, Audiences, Customer list. Minimum recommended size is 1,000 matched users for Search, 100 for YouTube and Display.
Match rates on Google trend slightly lower than Meta. Email match: 45 to 65%. Phone match: 25 to 50%. Lists carrying both fields fare better.
Remarketing lists for Search Ads (RLSA)
RLSA lets you bid differently when someone in your customer list searches a relevant term on Google. A returning customer searching “[your cuisine] near me” should see your ad at the top of the page every time, even if you do not bid aggressively to cold searchers. Bid plus 25% to plus 50% on RLSA audiences.
Display and YouTube retargeting
Build a remarketing audience from your Google Ads tag (all visitors, 30 days) and run display image ads and 6 to 15 second YouTube bumpers. Display retargeting CPMs are cheap ($3 to $8). Use it for top-of-funnel reminder ads, not conversion-driving offers, because display click-through is too low to convert offers efficiently.
Defining the Lapsed Customer: Why 90 Days Is Wrong for Most Concepts
Most articles tell you a lapsed customer is anyone who has not visited in 90 days. That is wrong for most restaurant concepts. A lapsed customer is concept-specific, and the right window is the one that catches a guest before the habit fully breaks but after they have slipped past their normal cadence.
The way to find it: pull your POS data, calculate the median visit interval for repeat customers (people with 3-plus visits), then multiply by 1.5 to 2x. That is your lapsed window.

For most operators on Toast or Square you can pull the report directly. For everyone else, sample 100 repeat customers, average the gap between their visits, multiply by 1.5, and use that as your lapsed window. Then build the segment in your email platform: customers whose last visit was more than one lapsed window ago but less than 365 days ago.
That segment is your win-back retargeting audience. Sync it to Meta as a separate Custom Audience and run dedicated win-back creative against it. Restaurant customer retention covers the lapsed-flow logic on the email side, which mirrors the ad side.
Win-Back Creative That Actually Works: Five Frameworks
The audience is half the battle. Creative is the other half. Generic “we miss you, here is 10% off” ads get ignored. These five frameworks consistently outperform.
Framework 1: Concrete-offer return
“$10 off your next visit, expires Sunday.” Specific dollar amount, hard expiry. Outperforms “20% off” by 15 to 30% on CTR because $10 reads as more concrete than a percentage. Use for the 60 to 90-day lapsed audience. Pair with a single hero image of a signature dish.
Framework 2: New-menu-drop announcement
“Five new dishes you have not tried. Come see what is new.” No discount. The hook is curiosity. Use for the 90 to 180-day lapsed audience where a discount might attract the wrong segment (people who only come for deals). Run it every quarter when you actually update the menu.
Framework 3: Milestone personalization
“It has been 47 days since your last visit. We saved your favorite table.” Hardest creative to build because it needs Klaviyo (or similar) flow integration passing dynamic fields to Meta CAPI. Done right, conversion lift is 25 to 60% versus static. Use for the high-LTV lapsed segment.
Framework 4: Social-proof retarget
UGC video, a customer review, a “voted best [cuisine] 2025” tagline. Builds trust before the offer. Use for pixel and engagement audiences where the customer has not committed yet. Strongest in the consideration stage, not the win-back stage.
Framework 5: Event or celebration
“Wine dinner Friday, 10 seats left.” Urgency, occasion-driven, no discount needed. Use across list, engagement, and video audiences for time-bound events. Highest CPC performance because intent is locked to a date.
The carousel format wins for restaurants. Four to six menu items with prices, then a final card with the offer and CTA. Carousel beats single-image by 30 to 50% on CTR in restaurant retargeting based on account testing. Restaurant Facebook ads goes deeper on creative production.
Frequency, Budget, and Bid Strategy
Retargeting that runs at the wrong frequency or budget burns money or alienates customers. Three settings to dial in.
Frequency cap: 3 to 5 impressions per week
Inside Meta, the Reach objective lets you set a hard frequency cap. For other objectives, you control frequency through audience size and budget pacing. Aim for 3 to 5 impressions per week per person. Above 5 per week, comments turn negative (“why am I seeing this so much”). Below 2 per week, you do not get enough reps to drive conversion.
Target frequency math: (monthly impressions / audience size) across the month, tuned to roughly 12 per person per month, which lands at 3 per week. A $1,500 monthly budget on a 5,000-person audience at a $5 CPM buys 300,000 impressions, or 60 per person per month, which is too hot. Either shrink the audience, lower the budget, or widen the cap. The point is to do this math before launch, not after the complaints.
Budget split: 30% prospecting, 70% retargeting (under 5 units)
For independents and small groups, the split that wins is 30% cold prospecting and 70% retargeting. For multi-unit operators (10-plus units) the prospecting share grows to 50% because the first-party audience starts to saturate. Some operators flip this to 90/10 in the first 90 days while building the data foundation, then rebalance once the lists mature.
Bid strategy: lowest cost, with a cost cap on the offer ad
Use lowest-cost bidding for the broad retargeting ad set. For the offer-driven ad sets (Framework 1), set a cost cap at 1.5x your historical cost-per-conversion. This stops Meta from chasing low-quality conversions when the offer spikes demand. Restaurant marketing ROI calculator handles the budget math if you want a structured tool.
Tracking In-Store Conversions
The hardest problem in restaurant retargeting is closing the loop between an ad click and a dining-room visit. The customer clicks Tuesday, comes in Saturday, pays with a different card than the one tied to the click. Meta’s default attribution never sees the visit. Three ways to solve it:
- Conversions API for online conversions: reservations on OpenTable or Resy, online orders on Toast or ChowNow, gift-card purchases. These fire conversion events server-side and track at 95%-plus accuracy.
- Offline conversion uploads: Meta Offline Conversions and Google Offline Conversion Tracking let you upload POS transaction data weekly with hashed identifiers. The platform matches the transaction to the ad click. Match rates are imperfect (40 to 70%) but the directional signal is enough to optimize.
- Store-visit conversions on Google: for accounts with enough location data and traffic, Google estimates store visits using device location signals. Use as a directional metric, not absolute truth.
For most restaurants the practical answer is: track online conversions accurately through CAPI, track offline conversions directionally through weekly POS uploads, and accept that some attribution will always go missing. The program still wins. Restaurant marketing automation covers the data-flow architecture.
Mistakes That Burn Your Retargeting Budget
Eight mistakes that show up repeatedly in restaurant ad accounts:
- Retargeting recent purchasers. Always exclude the last 7 days of converters from every retargeting audience. Showing a “come back” ad to someone who came in yesterday wastes budget and annoys the customer.
- Stacking the win-back offer on top of an existing email coupon. Customers who already had a Klaviyo discount waiting now see two competing offers. Suppress the email flow when the ad runs, or skip the email and use ads only.
- Audience too small. Below 1,000 matched users, Meta under-delivers and CPM spikes. Grow the audience or combine several into one ad set. This is the viability threshold in action.
- Audience too broad. “All website visitors, last 180 days” with no exclusions is not a retargeting audience, it is a stale list of mostly inactive users. Use 30-day windows with exclusions.
- Same creative for 90 days. Restaurant ad creative should rotate every 14 to 30 days. Ad fatigue is real and shows up as rising CPM and falling CTR.
- Pixel-only, no CAPI. Leaving 20 to 35% of attribution on the table because of iOS restrictions. Set up Conversions API once, benefit forever.
- Bidding too aggressively. Cost-cap bidding on warm audiences works only if your historical cost-per-conversion data is accurate. Otherwise default to lowest-cost.
- No exclusions across audiences. If pixel, list, and engagement audiences overlap heavily and you run them all at once with no exclusions, you double-charge for impressions to the same person. Exclude overlapping audiences from each other when they overlap by 30%-plus.
The 30-Day Restaurant Retargeting Launch Plan

Total ad spend across the first 30 days runs $400 to $850 for a single-unit independent. Total internal time is 19 to 31 hours, mostly front-loaded in weeks 1 and 2. Most operators do this with a part-time marketer or a fractional consultant, not a full agency.
Once live, ongoing time drops to 2 to 4 hours per week (creative refresh, weekly POS upload, performance review). The retargeting ad set runs as a permanent fixture, refreshed quarterly with new menus, seasonal offers, and event campaigns.
The efficiency gap, in one number. Across 60-plus restaurant ad accounts we have analyzed between 2024 and 2026, retargeting averages 4.8x ROAS (25th to 75th percentile of 3.2x to 7.1x). Prospecting averages 1.6x (0.9x to 2.4x). The retargeting line is roughly 3x more efficient at every cut of the data.
Putting It All Together
Restaurant retargeting in 2026 is not a complicated discipline. It is a sequence: clear the viability threshold, build the data foundation, define your audiences, produce the creative, launch at the right frequency, optimize weekly, and let the math compound. The hardest part is the foundation. The math after that is reliable.
If your current paid program is mostly cold prospecting and you have no retargeting layer, your most underused asset is sitting in your POS, your reservation system, and your email platform. Pull that data into a master file, hash it, upload it to Meta and Google, and start running win-back creative. Month one rarely produces magic. Month three is where the math turns undeniable. By month six, retargeting is the most profitable line item in the budget, year after year.
And if you are still under the viability threshold, the highest-leverage thing you can do is grow the list, not buy ads against a list that is too small to work. That is the job the Google Business Profile layer quietly does in the background. See Restaurant Velocity pricing if you want the discovery, review, and posting side running on autopilot while your first-party list compounds to retargeting size.
Frequently Asked Questions
What is restaurant retargeting?
How many customers do I need before retargeting is worth it?
What is the difference between retargeting and remarketing?
How big does my email list need to be for retargeting?
What is a good ROAS for restaurant retargeting?
What is the best Custom Audience for a restaurant on Facebook?
How do I retarget past customers using my email list?
How do I define a lapsed customer for a restaurant?
How often should retargeting ads show to a customer?
Does Google Customer Match work for restaurants?
How do I track in-store conversions from a Facebook ad?
Why are retargeting ROAS numbers so much higher than prospecting?
