Traveler 360 Data Platform for Airlines
Publication date: November 11, 2020 (Diagram history)
With this architecture, you can identify known and unknown travelers across all channels. Use customer interaction activity to execute offers and campaigns with high return on investment (ROI).
Airline companies often rely on a single vendor solution such as a customer data platform (CDP) or master data management (MDM) platform. This approach leaves gaps in capability, creates data silos, and prevents a full view of guests and activity across all channels. This architecture combines the best capabilities from CDP and MDM to build a true traveler 360 data platform. It provides unfettered access to business users and data scientists. It operationalizes traveler insights by making them available as services and business events.
This reference architecture builds upon the Personalization Using AI/ML for Airlines. It extends personalization to known and anonymous customers by using CDPs.
Traveler 360 data platform diagram
The following steps describe the architecture:
-
Use MDM tools to create a unified traveler profile. Identify loyalty members through addressable attributes such as email and phone.
-
The CDP client-side uses tag management and first-party cookies. Collect web and mobile activity from travelers.
-
The CDP server-side collects activity and identifies anonymous users. Augment profiles with loyalty and unified traveler data.
-
Process and curate all traveler activity in a data lake. Activity includes loyalty, reservations, check-ins, purchases, marketing, web, mobile, and call center data.
-
Traveler 360 microservices and business events personalize offers. Deliver targeted campaigns based on traveler profiles.
-
(Optional) Use the CDP to share anonymous traveler attributes with partners. Share only non-identifiable attributes.
Further reading
For additional information, see the following resources:
Diagram history
To receive updates about this reference architecture diagram, subscribe to the RSS feed.
| Change | Description | Date |
|---|---|---|
Initial publication | Reference architecture diagram first published. | November 11, 2020 |
RSS subscription requirement
To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.