Feast AnalyticsRestaurant Offer Halo Effect: What the Estimated $10 per $1 Tracked Meant

Restaurant Offer Halo Effect: What the Estimated $10 per $1 Tracked Meant

One restaurant saw full-price ribeye sales rise 131%. Its estimated $10-to-$1 offer halo was observed revenue lift, not proven profit.

Can promoting a restaurant offer also sell more of the dish at full price? In one Jersey City restaurant, full-price ribeye sales rose 131% during a ribeye campaign. The increase extended beyond the offer redemptions the restaurant could directly track.

That distinction matters when deciding whether a restaurant promotion worked. The offer can be responsible for some sales you cannot match, but a bigger week by itself does not prove the offer caused the difference.

The case started with one ribeye offer and a weekly sales baseline

The restaurant was a full-service New American restaurant in Jersey City, New Jersey. The intervention was a promoted ribeye offer, with offer revenue tracked separately from the restaurant's ordinary POS sales. The measurement window is the pre-offer weekly baseline versus the campaign-period report verified on July 9, 2026—not a fixed-duration experiment with a published start date.

Before the offer, whole-restaurant sales averaged $19,700 per week. During the reported campaign period, that average reached $30,800, a 56% increase.

The report also showed dinner revenue up 71.5% and full-price ribeye sales up 131%. A separate account of the case put dinner guests per week up 61%.

Those are observed changes in the restaurant's own records. They are stronger than impressions or clicks, but they still describe what changed during the campaign—not what would have happened without it.

“What are you doing with them to prove that ROI?”Restaurant marketing agency partner

That was an agency partner's question about the case. It gets to the hard part: the offer revenue was trackable, while much of the movement elsewhere in dinner service was not directly connected to an individual campaign response.

The $10-to-$1 figure was a halo estimate, not ROAS

The reported relationship was approximately:

estimated untracked dinner-revenue lift ÷ tracked offer revenue = about $10 per $1

In plain English, the founder estimated that dinner sales rose by about ten dollars outside the tracked offer for each dollar of tracked offer revenue. That compares two kinds of sales—not sales with ad spend—so it is not a 10x ROAS claim or a profit calculation.

The case supports two separate statements: full-price ribeye sales rose 131%, and the founder estimated roughly $10 in untracked dinner-revenue lift per $1 in tracked offer revenue. It does not support saying every one of those ten dollars was a full-price ribeye sale.

The likely halo ran through the dining room as well as the ad

The working explanation was visibility. Repeated promotion made the ribeye familiar before the visit, and plates arriving in the dining room made the item visible to guests who had not redeemed the offer. The restaurant owner also described the full-price increase as an estimate after removing offer redemptions, which is useful firsthand context but not a controlled causal result.

“Our philosophy is that it should be somewhat high perceived value, but not enough for someone to be super filled up and not order anything else.”Restaurant marketing team member

That was the campaign team's offer-design rule. The deal had to make the visit feel worthwhile without replacing the rest of the check.

The restaurant did not find its result on the first try. The report records three iterations before it reached the reported approach, which is a better lesson than treating one ribeye campaign as a universal recipe.

Look beyond redemptions without claiming every sale came from the offer

If you run a similar campaign, look at three things together: the sales tied to offer redemptions, full-price sales of the promoted item, and overall restaurant sales. Compare similar weekdays and dayparts before and during the campaign. Note price changes, holidays, or other events that could explain part of the difference.

That gives you a more useful picture than counting redemptions alone. An offer may introduce a dish to people who later order it without a discount. But a busier week is supporting evidence, not proof that every additional dollar came from that offer.

More sales also need to leave more money after the cost of serving the food and running the campaign. The case record does not provide enough detail to calculate that profit independently. For your own restaurant, make that calculation before increasing the budget; the restaurant marketing ROI guide explains how.

The result also should not become a universal ribeye recipe. Why restaurants should test more than one offer explains how a small comparison can reveal whether the offer fits the restaurant before a larger budget goes behind it.

Feast can show the tracked sale; the owner still has to judge the halo

Feast's full service connects campaign pages, follow-up SMS, ad management, and POS-linked campaign sales. Its reporting can show sales attributed to a campaign, but it does not turn the restaurant-wide change into proven incrementality or profit.

Book a demo of Feast.