Most hotels say email drives revenue.
Very few can verify this statement.
That alone would make email a weakly managed channel. The larger problem shows up earlier in the chain. In many hotel programs, subscriber value starts degrading almost immediately after capture.
Not because the guest got bored.
Not because the list aged.
Because the hotel handed common email infrastructure to people who do not have the skill to manage it.
Email is not just copy and design. It is infrastructure. A single campaign depends on domain authentication, rendering integrity, accessibility standards, and booking visibility. When the person running that system does not understand those standards, the hotel is not simply producing weaker marketing. It is introducing infrastructure failure into a revenue channel.
Benchmark Evidence
Across 30 hospitality brands reviewed in the latest Hospitality Email Benchmark Index, 21 were operating with either no DMARC policy or a p=NONE policy.
Twenty-five showed no dark mode support.
Fourteen scored zero on ALT text.
Six were still using image-based CTAs.
Several were missing plain text entirely.
One property could not verify the revenue attribution loop at all.
Those are not creative flaws.
They are infrastructure failures caused by lack of skill.
Infrastructure Failure
Hotels usually talk about list degradation as if it were a time problem. The list gets old. Subscribers stop opening. The audience loses interest. Performance softens over months, then years.
That happens.
The benchmark data points to another form of degradation that is more immediate and more dangerous. The subscriber record remains on the list, but the commercial value attached to that record begins collapsing almost at once because the message is weakly authenticated, poorly rendered, inaccessible, or disconnected from booking visibility.
The contact is still there.
The revenue path is not.
“Sent” is one of the most misleading words in hotel email reporting. Sent does not mean received. Received does not mean rendered correctly. Rendered correctly does not mean accessible. Accessible does not mean tied back to booking activity. A hotel can watch campaigns leave the platform all year and still have no clean line from subscriber to reservation to revenue.
Google requires bulk senders to authenticate outbound mail with SPF or DKIM, publish DMARC, and align domain identity. Yahoo has adopted the same baseline standards for high-volume senders. A hotel that leaves DMARC at p=NONE or has no DMARC record at all is not just overlooking a technical setting. It is tolerating weak control over a revenue path. That is not a strategic choice. It is a skill failure at the infrastructure layer.
Source: Google Email Sender Guidelines
Source: Yahoo Best Practices for Email Senders
Message Integrity Failure
Dark mode is not a fringe viewing environment. It is a normal part of how people read email now, especially on mobile devices. Litmus has documented that dark mode behavior varies sharply across email clients and that marketers must test for those conditions instead of assuming a design will hold. In this benchmark, 25 of 30 hotels showed no dark mode support. Management is often approving one version of the email while guests are seeing another. When buttons disappear, logos invert, or contrast collapses, that is not a brand problem. It is an infrastructure failure in message presentation.
ALT text is not a courtesy. It is part of the infrastructure that makes a message legible when images do not render and meaningful for people using assistive technology. WCAG requires text alternatives for non-text content for exactly this reason. WebAIM’s guidance is even plainer: missing or poor alternative text strips meaning out of digital communication. Fourteen of the 30 hotels in this set scored zero on ALT text. Several others were flagged with failures such as “All ALT tags empty,” “Most ALT tags missing,” or “92% missing ALT tags.” That is not just bad workmanship. It is lack of skill against a known standard.
Some hotels are still sending HTML-only messages or relying on image-based CTAs. The path to action can disappear when images are blocked, when assistive tools interpret the message poorly, or when rendering breaks in the client. The operator does not know how to maintain a resilient path to action inside a commercial message.
Source: Litmus — The Ultimate Guide to Dark Mode for Email Marketers
Source: W3C WCAG 2.1 — Success Criterion 1.1.1 Non-text Content
Source: WebAIM — Alternative Text
List Degradation
List degradation in this report does not mean the common industry definition of subscriber boredom, inbox fatigue, or slow audience decay.
List degradation here means near-instant commercial degradation.
A subscriber joins the list.
The subscriber record exists.
The revenue path begins failing almost immediately because the message does not reach the inbox, does not render correctly, does not remain legible, does not preserve the CTA, or cannot be tied back to booking activity.
The list still exists.
The commercial value does not.
That is why infrastructure failure and list degradation belong together. A hotel can believe it has a healthy list while the channel is quietly losing usable reach, message integrity, and booking visibility.
Booking Visibility Failure
One of the hotels in the benchmark is explicitly marked with “Revenue attribution loop unverified.” That point matters because it exposes the final unknown unknown. Even when a message is delivered and rendered, the hotel may still be unable to connect booking activity back to subscriber activity. That is a second-order infrastructure failure. Revenue may be generated, but it disappears from view, which means management cannot defend the channel, improve it, or trust the people running it.
The underlying measurement problem is already laid out in the Revenue Verification Loop.
If the booking path breaks, the operator loses the ability to answer three basic questions:
How much revenue came from email?
Which campaigns produced it?
Which subscribers generated it?
ADR Exposure
Put that against actual ADR.
In Palm Springs, the sampled set shows peak Saturday ADRs such as $499 at Avalon Hotel & Bungalows Palm Springs, $500 at Korakia, $550 at L’Horizon, $589 at Sparrows Lodge, and $614 at Holiday House. Those numbers sit inside a market already showing rate compression and uneven spread behavior in Field Report 003 — Palm Springs Pricing Volatility.
In Napa Valley, the numbers get sharper: Meadowood Napa Valley at $1,750, Auberge du Soleil at $2,070, Solage at $1,275, Stanly Ranch at $1,495, Carneros Resort and Spa at $1,349, and Four Seasons Napa Valley at $1,430. Those rates sit inside a market where pricing structure itself already demands precision, as shown in Field Report — Napa Valley Pricing Volatility.
At those rates, infrastructure failure inside email is not abstract.
Take a segment of 1,000 subscribers and assume a modest 1% booking opportunity from a campaign or sequence. That is 10 bookings.
At $499 ADR, that segment represents $4,990 in room revenue.
At $614 ADR, it represents $6,140.
At $1,275 ADR, it represents $12,750.
At $1,750 ADR, it represents $17,500.
At $2,070 ADR, it represents $20,700.
Two missed bookings at Four Seasons Napa Valley’s sampled peak Saturday ADR is $2,860.
Three missed bookings at Auberge du Soleil’s sampled peak Saturday ADR is $6,210.
Five missed bookings at Meadowood’s sampled peak Saturday ADR is $8,750.
Five missed bookings at Holiday House’s sampled peak Saturday ADR in Palm Springs is $3,070.
Unknown Unknowns
Unskilled, in this context, does not mean inexperienced in some vague sense. It means unable to execute and manage the common infrastructure required to send a single commercial campaign correctly.
The operator does not know Google’s sender standards.
The operator does not know accessibility standards.
The operator does not know how to account for dark mode.
The operator does not know how to protect a resilient CTA path.
The operator does not know how to verify the booking loop.
That is not a personality critique.
That is a capability problem.
That capability problem becomes a revenue problem the moment it sits inside the email channel.
Hotels often hide this behind downstream stories. Teams blame the list. They blame audience fatigue. They blame macro softness. They blame shifts in traveler behavior.
Sometimes those explanations are real.
This benchmark points to a more basic truth: many properties are blaming outcomes for failures that began in infrastructure.
The guest did not reject a functioning system.
The hotel failed to maintain one.
Conclusion
That is list degradation in near real time.
The subscriber joins the list.
The hotel sends an email that breaks inside the subscriber’s inbox.
The commercial value starts degrading immediately.
The hotel mistakes activity for function.
The damage compounds quietly.
A revenue channel should be managed like infrastructure, not theater. It should be authenticated, tested, accessible, and measurable. It should be possible to say not only that a campaign was sent, but that the domain met current sender standards, the message held across rendering environments, the content remained usable for the guest, and the booking path could be verified after the fact.
If those conditions are missing, the hotel does not have a reliable revenue channel.
It has email activity.
Email activity run by unskilled hands is an infrastructure failure with a room-revenue price tag.