Feast AnalyticsDoes Toast Track Where Customers Come From? What It Can and Cannot Attribute

Does Toast Track Where Customers Come From? What It Can and Cannot Attribute

Toast can report sales attributed to its own marketing. Outside campaigns need a separate connection from source to guest to settled check.

Toast can report sales that it attributes to marketing inside its own products. It cannot automatically know that an arbitrary Facebook ad, influencer post, flyer, or outside agency campaign caused a particular check unless that campaign is connected to an identified guest and the guest is connected to the settled Toast transaction.

That distinction explains why a restaurant can have detailed POS reports and still be unable to answer, “Which marketing actually brought these customers in?”

Toast knows the check better than it knows the outside source

Toast records the transaction: location, time, items, discounts, payment status, and whatever guest identity the restaurant collected. Its native marketing reports can then attribute sales according to Toast's own rules. Toast has also documented a Demand Attribution Dashboard that separates attributed sales into new, active, and reactivated guest segments.

Those reports can be useful. But “Toast attributed these sales” is not the same as “we directly matched this outside campaign to these paid checks,” and neither claim proves that all reported revenue was incremental or profitable.

Toast's loyalty product can enroll a guest at the register, through a digital receipt, during online ordering, or through a signup link, then connect points with purchases. That helps identify the guest. It does not recreate the campaign source if nobody captured that source earlier.

An outside campaign needs an identity that survives the visit

Suppose a guest sees an Instagram ad on Tuesday, remembers the restaurant, and walks in on Friday. Toast can record Friday's sale. Without a source-bearing response—such as a reservation source, offer claim, unique link, code, or another permitted identifier—there is nothing reliable to connect Tuesday's ad with Friday's check.

An agency operator described this blind spot directly:

“They don't click on that link. But they just come in the next day because they thought about it. I wouldn't get the attributed revenue towards them.”Agency operator

The visit may still have been influenced by the ad. It belongs in a careful analysis of observed lift, not in a list of directly matched checks.

For a direct match, the chain is:

campaign response → identified guest → completed Toast check

If one link is missing, say where the evidence stops. A click is a click. A reservation is intent. An arrived guest is a visit. A paid, non-voided check is a sale.

Keep Toast attribution, direct matches, and lift in separate buckets

Restaurants often end up comparing unlike numbers. The ad platform claims conversions, Toast reports attributed sales, and the operator notices that Friday felt busier. Each can contain useful information, but they do not prove the same thing.

An agency owner once heard a large awareness number and asked the question restaurant reports often avoid:

“We have brand awareness, check. Got it. Where's the sales?”Agency owner

Toast can provide the sales record at the end. The campaign still needs a reliable way to reach it.

Check the connection in your own restaurant

Before relying on a report, complete an authorized response through the actual campaign path and confirm that it reaches the correct settled check. Then confirm that voids and refunds are handled properly. Use an internal guest key and keep phone numbers, email addresses, payment details, and raw POS screenshots out of public reports.

Also measure how many eligible responses could not be matched. A matched-sales total without the unresolved group can look more complete than it is.

The right setup depends on how guests buy. Reservations, online orders, loyalty identity, offer claims, and walk-ins create different paths. Toast does not need to originate every campaign, but the source identity has to reach the guest record before the settled check can carry it.

Feast connects outside marketing to the Toast sale

Feast is useful when Toast holds the completed transaction but the restaurant still needs a managed connection from the campaign response to the guest and check. Feast's documented flow connects an identified campaign response with an in-store action and supported POS transaction; Toast is among the supported systems.

That produces matched sales under the stated matching rules. It does not turn anonymous views into known customers or automatically prove incrementality and profit.

If you want to connect outside campaigns to Toast checks, Book a demo of Feast.