The average was clean. The properties were not.

A portfolio average can place an airport hotel, a conference resort, an extended-stay property, and a historic urban hotel on one line. The arithmetic is valid. The implied comparison may not be.

Each property serves a different mix of customers through different inventory, markets, seasons, channels, investments, ownership arrangements, and operating constraints. A ranking that ignores those conditions can reward structural advantage and call it execution. It can also turn a real local problem into an excuse by allowing every team to declare itself incomparable.

Shared measurement needed a dictionary

Google's 2022 Analytics 4 guidance described event-based measurement, customer journeys, privacy controls, subproperties, and roll-up properties. It was broad digital-measurement guidance, not a hospitality governance model. The direction was still relevant: enterprise reporting was becoming flexible enough to preserve different teams and purposes inside a common measurement environment.

That flexibility did not decide what a completed pathway meant. Portfolio leaders still needed a measurement dictionary: the event being counted, its population, source, time period, attribution rule, owner, and known limitation. Until those definitions matched, a comparison of conversion or engagement rates looked more precise than it was.

Public filings showed why context mattered

Marriott's 2022 filing described a business spanning brands, price points, regions, managed properties, franchised properties, and different contractual relationships. Host Hotels & Resorts described another portfolio shaped by property type, manager, market, investment, and ownership considerations. Neither filing prescribed a digital-content metric.

They did establish the organizational fact beneath the dashboard. Shared oversight does not make local businesses identical. A property receiving early discovery traffic may produce longer exploratory sessions than one whose visitors arrive from a qualified proposal. A smaller property may answer the buyer quickly because there are fewer relevant combinations. More activity is not automatically better understanding.

Context needed structure, not special pleading

Local explanation becomes credible when it is governed. Market events, inventory changes, renovations, channel shifts, content updates, staffing conditions, and known data defects need dates, sources, owners, and review status. The same fields should be available to every property.

SiteSee can keep that local evidence attached to common portfolio measures. Leaders can compare what is genuinely comparable while local teams explain the conditions that affected the customer path. Privacy and access controls remain essential, especially when small audience segments could expose personal or commercially sensitive information.

This follows the earlier argument that consistency should protect meaningful differences. The portfolio standard defines the question. Local context helps leaders answer it responsibly.

The ranking became a better question

The purpose of the dashboard was never to make every property look the same. It was to help leadership see where a result deserved attention, which practice might transfer, and what still required investigation.

Once context entered the review, the ranking lost some of its drama and gained practical value. First and last were no longer verdicts. They became the beginning of a better question: what happened here, under these conditions, and what can the rest of the portfolio responsibly learn from it?