# Guest identity resolution: solving the single-view-of-guest problem
A traveler named Maria has stayed at the same hotel group 14 times in three years: twice under "Maria Garcia," three times as "M. Garcia," once with a typo ("Maria Grcia"), and the rest booked by her assistant using a corporate email. Add a loyalty account opened at a different brand within the group, a wedding block booking, and a mobile app profile made from her phone's autofill. Result: the hotel group's systems believe Maria is 12 different people. She gets a "welcome back, first-time guest" email on her 14th stay.
This is the single-view-of-guest problem, and it costs the industry real money in misdirected marketing, duplicated loyalty points, and guests who feel like strangers despite years of spend.
Hospitality data is fragmented by design, not accident. Each system was built to solve a local problem, not a company-wide one.
The main sources of fragmentation:
A franchised hotel group with 5,000 properties might run dozens of PMS versions across brands acquired over decades (this is a well-documented industry pattern, seen at large multi-brand groups such as Marriott and IHG, which have grown substantially through acquisitions). Each acquisition imports its own guest database, its own ID format, its own dataown dataData collected directly from your own customers and prospects through your own channels: your most reliable and privacy-compliant source.View full definition → quality baseline.
Identity resolution is the process of deciding, algorithmically, that multiple records refer to the same real person, then merging them into a "golden record."
Deterministic matching looks for exact or near-exact agreement on strong identifiers:
This is high-confidence but limited: it misses Maria's typo, her assistant's email, and her maiden-name booking.
Probabilistic matching (also called fuzzy matching) scores similarity across weaker signals and combines them into a confidence score:
A simplified version of how a matching engine scores a candidate pair:
score = 0
if email_exact_match: score += 40
if phone_exact_match: score += 30
if name_similarity > 0.85: score += 15
if address_match: score += 10
if payment_token_match: score += 25
if score >= 50: auto_merge
elif 30 <= score < 50: flag_for_human_review
else: keep_separateThresholds like these are tuned by data teams to balance two error types: false merges (accidentally combining two different guests, a privacy and trust risk) and false splits (failing to unify one real guest, the original problem).
Identity resolution lives or dies on data qualitydata qualityThe degree to which data is fit for purpose: accurate, complete, consistent, timely, valid and unique. Poor quality data undermines analytics, reporting and AI.View full definition →. The core metrics data teams track:
Identity resolution is not just a technical exercise, it operates inside real legal constraints.
GDPR (General Data Protection Regulation), the EU's data protection law, requires a lawful basis for combining personal data across systems and gives guests the right to access, correct, or delete their unified profile. A merged golden record makes fulfilling a Subject Access Request (a guest's legal right to see what data is held on them) easier in principle, but it also means a single deletion request now needs to unwind data across every source system it touched.
In the US, there is no single federal privacy law equivalent to GDPR, but CCPA/CPRA (California Consumer Privacy Act, updated by the California Privacy Rights Act) grants similar rights to California residents, and hotel groups operating nationally often apply the stricter standard everywhere for simplicity.
Practical governance questions for hospitality data teams:
For a practical primer on the legal basis requirements, the UK Information Commissioner's Office publishes a clear guide: ICO: Guide to GDPR.
Knowledge check
1. In the Maria Garcia example, what is the root cause of the hotel group's systems perceiving her as 12 different guests?
2. Why does a booking made through an OTA (like Booking.com or Expedia) pose a particular challenge for identity resolution?
3. A hotel group wants to reduce single-view-of-guest problems. Which situation would most directly require identity resolution logic to merge records rather than simply adding a new field to an existing database?
4. Select ALL correct answers describing sources of guest data fragmentation mentioned in the lesson.
Select all the correct answers.
5. Select ALL correct answers about the real business consequences of the single-view-of-guest problem described in the lesson.
Select all the correct answers.
Once identity resolution is working, it should show up in measurable outcomes, not just cleaner dashboards.
Key benchmarks data and analytics teams track post-implementation:
A simple worked example: if a hotel group has 10 million "profiles" but identity resolution reveals only 7.5 million unique guests, the effective duplication rate is (10M − 7.5M) / 10M = 25%. Every marketing campaign sent without deduplication was over-counting reachreachThe number of unique people exposed to your message in a given period. Unlike impressions, reach counts each person once, no matter how often they see it.View full definition → by a quarter, and potentially emailing the same guest three times under three names.
🎬 [VIDEO: "What is Customer Data PlatformCustomer Data PlatformA Customer Data Platform unifies customer data from all sources into persistent, actionable profiles that other systems can use.View full definition → (CDPCDPA Customer Data Platform unifies customer data from all sources into persistent, actionable profiles that other systems can use.View full definition →) and Identity Resolution?" - youtube.com - a vendor-neutral explainer on how identity graphs are built and used in customer data platforms, applicable directly to hotel guest data]