Campaign (vs. Journey)

Campaigns are the oldest feature in marketing software and every email tool has them. The hospitality version differs in two places. The list is built from reservation and check history rather than from a signup form, and the result is counted in bookings and covers rather than in inbox statistics. Both of those depend on a guest record that spans systems. Holding that record is the job of a restaurant CRM, sometimes called a guest data platform.

What is the difference between a campaign and a journey?

A campaign is one send on a date an operator picks. A journey, also called an automation, is a standing rule that sends to one guest at a time whenever that guest meets a condition. The holiday party announcement is a campaign. The note that follows a guest’s first visit is a journey, and it goes out on that guest’s schedule rather than on the marketing calendar.

Two things follow from that. A campaign is read by everyone on the list at roughly the same moment, so it can be topical: a new tasting menu, a closure, a patio reopening. A journey has to make sense to any guest who triggers it on any day of the year, so it cannot reference anything time-bound. Operators who forget this end up with a win-back email mentioning the summer patio arriving in February.

The second is maintenance. A campaign is finished the moment it sends, and a bad one is embarrassing once. A journey keeps running against whatever the data says today, so a rule that stops describing the restaurant accurately keeps sending anyway. A journey built around a set menu that changed in the spring will still be inviting guests back to it in the autumn.

When should a restaurant send a campaign instead of building a journey?

Send a campaign when the reason for the message sits on the restaurant’s side. A new chef, an event with a fixed date, a menu change, a private dining push into a slow February, a closure for renovation. No guest behavior can trigger any of those, because the news does not come from the guest.

Build a journey when the reason sits with the guest. A first visit, ninety days without one, a booking made for a birthday, a large party that spent unusually well. Those events arrive on their own timetable and they arrive continuously, so a rule handles them better than a person watching a report.

Most programs run both and the split is usually uneven. Journeys carry the recurring relationship work, campaigns carry announcements, and the announcement volume is what operators tend to overestimate. The plan can decide part of this too. Entry tiers in this category sometimes include a limited number of journeys and no broadcast campaigns at all, so it is worth checking which of the two a subscription actually covers.

How do you know whether a restaurant campaign worked?

A restaurant campaign is reported in bookings, visits and revenue rather than in opens, because the platform that sent the message also holds the reservation and check history for the same guest. The chain runs from the send to a guest who later appeared in the book or on a check, inside a defined attribution window.

The mechanism deserves precision, because it is not a click that reaches a table. A guest usually has to interact with the message first, by opening it or replying to it, and that interaction is what makes the guest eligible for credit. The platform then looks for a booking, a visit or spend from that guest inside the window. So the number reported is revenue and the qualifying event behind it is still an engagement.

Two consequences are worth holding onto. Attributed revenue is not caused revenue, since regulars who were coming anyway sit in most segments and will convert on almost anything sent to them. And a campaign to guests whose checks never match to a profile will read as weaker than it was, because the visits it produced were never attached to anybody.

Can I run restaurant campaigns from Mailchimp or Klaviyo?

For sending, yes. An email platform will deliver a campaign to a restaurant’s list and report opens, clicks and unsubscribes accurately, and where an online store is connected it will tie a send to a web order. What neither tool holds is the reservation book or the check. A restaurant working this way builds segments out of email behavior and measures results in clicks. That is a different program rather than a smaller one.

The gap shows up first in the segment. “Guests who opened the last three emails” and “guests who came twice in the last six months and spent above average” select almost entirely different people, and only the first can be built without visit data. A general CRM such as HubSpot has no native connection to a reservation platform, so bridging one takes custom integration work, and the connectors that exist mostly pull bookings in as marketing contacts rather than reconciling them against what the table spent.