Notifications
Clear all
Topic starter
08/07/2026 6:58 pm
TL;DR: A single customer view unifies booking, loyalty, behavioural, and service data into one real-time profile, and Comarch argues that travel brands need it to improve personalization, loyalty, and revenue. The deeper lesson is that fragmented identity data creates governance debt across every customer touchpoint, not just a marketing problem.
NHIMG editorial — based on content published by Comarch: Beyond the Booking, What Is a Single Customer View for Travel?
By the numbers:
- A stunning 87% of travel and hospitality data leaders agree that consumer behavior data is crucial to their team's business decisions.
- A remarkable 90% of companies say a Single Customer View reduces costs, while 80% view it as a significant sales driver.
- The global volume of data is staggering, reaching 149 zettabytes in 2024.
Questions worth separating out
Q: How should organisations build a single customer view without creating duplicate identities?
A: Start by defining authoritative sources for key identifiers, then establish deterministic and probabilistic matching rules that determine when records should merge.
Q: Why does fragmented identity data weaken customer experience and governance?
A: Fragmented data forces teams to act on partial context, which causes poor recognition, inconsistent service, and missed commercial opportunities.
Q: What signals show that a single customer view is not working well?
A: Frequent duplicate profiles, inconsistent loyalty recognition, stale attributes, and delayed response to customer events are all signs of failure.
Practitioner guidance
- Inventory identity source systems List every system that contributes to the customer profile, then document which attributes each system owns and which teams are accountable for reconciliation.
- Define matching and merge rules Specify the identifiers, confidence thresholds, and exception handling used to decide when two traveler records belong to one profile.
- Set real-time update thresholds Identify the customer events that must trigger immediate action, such as delays, loyalty status changes, or service escalations, and separate them from batch-only updates.
What's in the full article
Comarch's full blog post covers the operational detail this post intentionally leaves for the source:
- Specific feature explanations for booking, loyalty, CRM, and service data ingestion
- Vendor examples of how a single customer view supports travel personalisation workflows
- Detailed customer stories from Heathrow Airport, SAS, and Vietnam Airlines
- The practical checklist used to decide when a travel business should invest in SCV
👉 Read Comarch's analysis of single customer view in travel →
Single customer view in travel: what IAM teams can learn?
Explore further
08/07/2026 7:22 pm
Identity fragmentation is the real governance problem hiding inside customer experience language. The article presents personalization and loyalty as commercial outcomes, but the operational dependency is identity correlation across systems that were never designed to agree. That is the same class of problem identity teams face with machines, customers, and employees alike. Practitioners should treat every fragmented profile as a governance defect, not a marketing inconvenience.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to Ultimate Guide to NHIs.
- 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures.
A question worth separating out:
Q: How do travel organisations decide whether to invest in single customer view now?
A: Invest when customer records are split across core systems, when teams cannot reliably recognise the same traveler across touchpoints, or when personalisation remains shallow. Those are signs that the identity layer is constraining both revenue and governance, not just analytics maturity.
👉 Read our full editorial: Single customer view in travel exposes the cost of fragmented data
