Single customer view in travel exposes the cost of fragmented data

At a glance

What this is: This is a travel-industry analysis of single customer view, showing that unified customer data drives personalization, loyalty, and revenue while disconnected systems create fragmented identity records.

Why it matters: It matters to IAM practitioners because the same identity stitching, data quality, and lifecycle issues that affect customer profiles also shape NHI, autonomous, and human identity governance.

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.

👉 Read Comarch's analysis of single customer view in travel

Context

A single customer view is one unified profile that links identity, behaviour, and transaction history across disconnected systems. In travel, the governance problem is not a lack of data, but a lack of reliable identity stitching across booking, loyalty, CRM, and service platforms.

When identity data is fragmented, organisations misread the customer and miss the operational moment where recognition matters. That same pattern shows up in identity programmes whenever records, entitlements, or lifecycle events are split across tools and teams, which is why the Ultimate Guide to NHIs remains a useful reference point for unified identity governance.

Key questions

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. The goal is not to centralise every field, but to create a governed profile with clear ownership, auditability, and exception handling for conflicts or uncertainty.

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. It also creates governance risk because no one can reliably tell whether a profile is complete, current, or duplicated across systems.

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. If teams can explain the customer only after the journey is over, the profile is not operational enough to support real-time decisions.

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.

Technical breakdown

Identity resolution across booking and loyalty systems

Identity resolution is the process of determining that multiple records belong to the same person, even when identifiers differ across systems. In travel, that can mean matching an email address, a booking reference, a loyalty number, and browsing activity into one profile. The hard part is not storage, but correlation rules, duplicate suppression, and handling partial or contradictory attributes. Without strong resolution logic, the unified profile becomes a fragile merge of incomplete records rather than a dependable customer view.

Practical implication: map the identifiers and matching rules that currently create duplicate traveler profiles.

Real-time action layers and operational decisioning

A single customer view only becomes useful when it can inform action while the journey is still unfolding. Real-time action layers connect the profile to offers, service recovery, loyalty rules, and event-triggered workflows. In practice, this turns the profile into a decision engine rather than a static database. The architectural issue is latency. If updates arrive too late, the system can describe the customer accurately but still fail to influence the current interaction.

Practical implication: define which traveler events must trigger immediate decisions instead of batch updates.

Data silos, governance, and customer identity quality

Data silos do more than slow analytics. They create governance blind spots where different teams act on different versions of the same identity. That is why a single customer view depends on consistent data stewardship, source-of-truth decisions, and lifecycle handling for stale or conflicting records. In identity programmes, the same pattern appears when access, entitlement, or profile data is distributed without a common governance model. The technical challenge is therefore both integration and trust in the underlying identity data.

Practical implication: assign clear ownership for identity quality, reconciliation, and stale-record remediation.

NHI Mgmt Group analysis

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.

Single customer view is a useful analogue for NHI governance because both depend on a reliable master identity record. When booking, loyalty, CRM, and service data diverge, the organisation cannot trust the profile enough to act consistently. NHI programmes see the same failure when service accounts, tokens, and workload identities are tracked in separate tools with different ownership. The lesson is that identity completeness is a control surface, not a reporting nicety.

Identity resolution is the named concept this article makes concrete. It describes the discipline of deciding when multiple identifiers belong to one subject and when they do not. In travel, that determines whether the brand recognises the customer correctly; in IAM and NHI governance, it determines whether lifecycle and entitlement decisions are made against a trustworthy identity record. Practitioners should view resolution quality as a foundational control, not a downstream data-cleanup task.

Real-time decisioning changes the governance standard from visibility to responsiveness. A profile that updates too slowly can still support analytics, but it cannot support operational recognition at the moment it matters. That distinction matters across identity programmes because delayed state changes create gaps between what the organisation knows and what it can safely do. The practitioner takeaway is that timing is part of identity integrity.

The article reinforces that identity governance breaks first at the boundaries between systems, not inside them. Once records are split across booking, loyalty, marketing, and service platforms, the organisation loses consistency, context, and accountability. The same boundary problem drives many NHI and human identity failures. Practitioners should look for the joins where identity meaning is reconstructed, because that is where control failure usually begins.

From our research:

• 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.
• Ultimate Guide to NHIs also shows that 97% of NHIs carry excessive privileges, which is why identity visibility and entitlement scope must be linked.

What this signals

Identity convergence will become a shared requirement across customer, workforce, and machine records. Travel brands are learning that a profile is only as useful as the quality of the links behind it, and the same logic applies to IAM and NHI programmes. Once you accept that recognition depends on correlation, you can no longer treat identity quality as a back-office data concern.

Service-account visibility is a useful benchmark for any profile-governance programme. Only 5.7% of organisations have full visibility into their service accounts, according to Ultimate Guide to NHIs, which shows how hard it is to maintain a trustworthy identity inventory even in machine contexts. The lesson for customer identity programmes is that completeness must be designed, measured, and owned.

A stronger model will connect identity resolution, lifecycle events, and real-time orchestration rather than treating them as separate projects. That shift matters because the business value of a unified profile appears only when the underlying identity state can be trusted at the moment a decision is made.

For practitioners

• 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.
• Review stale and duplicate records regularly Use periodic data-quality checks to find duplicate profiles, conflicting attributes, and dormant identities that distort service and loyalty decisions.

Key takeaways

• A single customer view solves an identity governance problem first and a personalisation problem second.
• Fragmented profiles create the same kind of operational blind spots that identity teams already manage across human and non-human records.
• Organisations that want real-time recognition must govern identity quality, merge rules, and update latency as core controls.

Key terms

• Single Customer View: A single customer view is one governed profile that combines records from multiple systems into a unified representation of one person. It depends on identity resolution, source ownership, and update discipline so the profile stays current enough to support service, loyalty, and decisioning.
• Identity Resolution: Identity resolution is the process of determining when separate records refer to the same subject. It uses matching logic, confidence thresholds, and exception handling to reduce duplicates and conflicting identities, whether the subject is a customer, employee, service account, or other governed identity.
• Real-Time Action Layer: A real-time action layer turns a profile from a reporting asset into an operational control point. It listens for identity or event changes and triggers offers, service recovery, or other decisions while the interaction is still live, which makes timing part of governance.

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

👉 Comarch's full post covers the travel-specific implementation examples and success stories.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity security strategy or governance in your organisation, it is worth exploring.