Every platform claims the same table
Meta, Google and the delivery apps each grade their own work. Add their conversions together and they claim more guests than your POS recorded.
Countlift for Restaurant groups
Countlift reads daily covers and check revenue from your POS, compares each location that got media with a matched twin that didn’t, and shows which markets your ads actually filled.
The problem
Meta, Google and the delivery apps each grade their own work. Add their conversions together and they claim more guests than your POS recorded.
“Get directions” and menu views don’t tell you whether a party sat down. The register does — and it’s the number your owners already trust.
Your busiest locations fill on a Friday no matter what. Without proof by location, spend follows last year’s plan instead of where it adds guests.
What you'll see
Extra covers against matched locations without the media, not clicks or platform conversions. Sample data, not a customer result.
Winter Park and Pearl fill without help. Move their social budget to Houston and Tampa, where each $1k adds about 65 covers.
How it works
Typical setup: Daily POS totals by location + ad accounts.
Native connectors where they exist; a daily file upload everywhere else.
Each market with media is measured against a MarketTwin™, a blend of matched markets without it. Every result gets a 95% range and a confidence grade. How the engine works →
Get suggested budget moves, a weekly Slack summary and a monthly Proof Report.
Moments it measures
Opening Lift compares each new location with a matched twin from day one, even with no sales history. Reuse the launch playbook that worked.
See the covers and check revenue a menu or holiday push added in markets with media, not just the promo codes redeemed.
Run CTV or billboards in a few markets, hold the rest back, and read covers per location before you scale the buy.
Channels it proves
Radio, billboards, mailers and creators are logged as spend by market and measured the same way.



FAQ
No. Countlift reads daily totals by location — guest counts (covers) and check revenue. No guest names, emails, card numbers or order details are needed or stored.
Toast is a native connector: an admin enables Countlift under Integrations in Toast Web, and daily totals sync on their own. Square is native too. Clover, Olo and OpenTable use a daily export upload.
If your POS records them by location, they’re in the totals Countlift reads. To judge dine-in campaigns on dine-in guests only, export dine-in covers and leave delivery out.
No card. Daily covers by location is all it takes.