Track walk-ins from your ads with a QR code menu

Tuesday: why the ad gets no credit

An ad platform can only credit what it can see. A tap on a link, a call button, a booking or a purchase on a website each leaves a signal the platform reads back and ties to the ad that came before it. A guest who watches your happy hour video on Tuesday, remembers it on Friday and walks in at six leaves no signal at all. The visit happens, the check gets paid, and the campaign that caused it reports nothing.

That gap costs more than a line in a report. With no visits to learn from, the platform spends your budget on the people most likely to tap, who are often not the people most likely to walk in. You see a cheap cost per click, a quiet Thursday and no way to say which of your two campaigns filled the bar on Saturday.

For a restaurant that lives on walk-ins, this is most of the business. A taproom, a cafe, a lunch counter or a neighborhood spot with a patio may take a few bookings a week and hundreds of guests who simply show up. When those guests are invisible to your ads, the ads are judged on the smallest part of what they do.

Friday, table 12: what one scan records

The guest sits down at table 12 and points a phone camera at the code on the table tent. Your menu opens, and one scan is counted under that code, on that day, at that placement. A placement is simply the name you give a code, so "Table 12", "Patio" and "Bar top" each keep a count of their own. Every code shows its total, this week and a 30-day chart, and your busiest placements are ranked side by side.

The record is small on purpose. A scan keeps the time, the kind of phone and a rough region, never the guest's internet address, and it is deleted after 180 days. There is no app to download and no account to create: the code opens an ordinary web page with your menu written as real text, a photo and a price beside each dish.

Read the count as a steady signal. Every scan adds one, so a guest who opens the menu twice counts twice. Because it is the same kind of count every week, its movement is what tells the story: scans that climb while an ad runs and settle when it stops say something a guess never could.

The same moment: an in-store visit reaches your ads

The link inside every code carries an ad-credit tag. It is always on; it is not a setting someone can forget to switch on. Once your Facebook and Instagram ad account is connected and the walk-in result is set up in it, which our team does with you once, each scan at table 12 is reported to that account as an in-store visit.

Tableify sends the visit and nothing more. It never learns the guest's name and never decides which ad earned the visit. That matching happens inside the ad platform, under its own rules: it checks whether the person who scanned had seen or tapped one of your ads, and if so it credits the visit to that campaign.

Campaign tags you add to a code also show up in your website numbers, so a code printed on a flyer, a window sign or a poster at the bus stop can be read the same way as the one on the table.

A week later: the credit beside each campaign

The visits your ad platform credits appear in your Tableify account next to each campaign's clicks and spend, so one screen answers a question that used to take three. Give it two or three weeks before you move money. One busy Saturday after a street fair says more about the fair than about the ad, so compare the same days of the week and note the outside events that bring crowds of their own.

Your dashboard can also turn credited visits into a dollar estimate: the visits the platform credits, times an average walk-in value you set. With sample numbers, 40 credited visits at a $35 average reads as $1,400. It is an estimate, not checks matched to guests, so set the average from your own sales and keep it on the low side. A modest figure that holds up beats a big one nobody believes.

The useful question is rarely what an ad made to the dollar. It is which campaigns bring people through the door and which only bring taps, and credited visits answer that well enough to stop paying for the second kind.

The next month: campaigns that aim for the door

With visits coming in, set up a walk-in goal and run campaigns that aim for it instead of clicks. The platform then looks for more people like the ones who came in and scanned, which is exactly the audience a walk-in restaurant wants. It needs some volume to learn, so give a campaign a few weeks and resist changing it every other day.

A goal can be built from all of your codes or from a single one. If the patio is the part of the room you most want filled on summer weeknights, build the goal from the patio code, and the campaign learns from the guests who actually sat out there.

Later: the guests who scanned become an audience

Guests who scanned at your tables can be gathered into a "scanned the menu" audience, kept for 90 days by default and up to 180. Show them a follow-up ad weeks later: the weekday lunch special for the office crowd who came in on a Friday, the trivia night for the Sunday regulars, the private room for the guest who arrived with ten friends.

These are people who have already sat at your tables, so the ad is a reminder rather than an introduction. If you would rather not build the ads yourself, Dex, the AI ads specialist, builds them from your content and launches them only on the budget you approve.

Placing codes so table 12 really means table 12

One code for the whole room tells you how many scans happened. One code per area tells you where. Give the dining room, the bar, the patio and the takeout window their own codes, or give each table its own, and the daily counts start answering real questions: does the patio crowd come from the summer ads, does the bar fill on its own.

Put the tent where the menu is needed, in plain sight at the moment a guest decides what to order. A code hidden behind a candle does not get scanned, and a tent that tips over on a windy patio ends up in a bus tub. Our team designs print-ready table tents around your code and your photos. When the menu changes, change where the code points; the printed tents stay put, and a code you switch off sends guests to your homepage.

• Dining room: one tent per table, facing the seat a guest takes first.
• Bar top: a code every few seats, low enough to read without leaning over a drink.
• Patio: a weighted tent, or a sticker on the table itself.
• Takeout window: a code by the register for guests reading while they wait.

Where walk-in tracking pays off most

It earns its place when most of your guests walk in and you advertise on Facebook or Instagram, or plan to. Bars, taprooms, cafes, slice shops with seating and neighborhood spots with a patio fit that description. Even before the first ad runs, the codes count scans by table, window and bar and open a menu guests can read. Skip it only if you never want to know whether your ads bring people through the door.

Walk-ins and bookings live side by side on the same site. Guests who plan ahead use the reservation system on your own website, and the same pages help hungry guests find you before they walk over; the restaurant SEO guide covers that side, and the fit checklist walks through the rest.