One guest.The whole context.
A booking, a WiFi connection, a conversation. Bring together the signals your hotel already knows and give your team a shared place to work from.
Three signals. The same person.
Explore the sources and see what each one adds. This profile and all its data are synthetic.
Contact email
Example identifierStay from 21 to 24 September
Same email in this examplePreferred language: Spanish
Same email in this exampleAlex Martín
Example guest
- EmailWiFi
- alex.martin@example.com
- Example reservationReservation
- 21–24 Sep · 3 nights
- Recorded preferenceCRM
- Service in Spanish
A connection starts the journey.
The portal provides a contact email. In this example, that identifier will be the link between all three records.
The booking adds the stay.
The reservation record uses the same email and adds the stay dates. The profile keeps that information alongside its source.
A conversation adds a preference.
The team records a preferred language in the CRM. It adds context for serving the guest; it does not create marketing consent.
Every detail keeps its source.
The email, stay and preference sit together in an illustrative profile. The team can understand the journey while treating identity and permission to send campaigns separately.
Motion supports the story; you can pause it.
Data matters. What you can do with it matters more.
A shared guest view
Read contact details, stays and activity in the same context, keeping a reference to where each signal came from.
Groups that make sense
Build segments from the information available: a previous stay, a recorded preference or a specific interaction.
A relevant next step
Use that context to prepare a conversation or a communication, respecting each person’s permissions and preferences.
From separate signals to a continuing relationship.
A profile becomes useful when it connects information to a specific task at your hotel.
Connect the sources
Review the data from your PMS, WiFi portal and CRM that can enter the journey. Each connection depends on your provider, fields and hotel setup.
Your installation is the starting point.Relate the identities
Available identifiers help relate records. Check the matches and preserve the source of each detail; incomplete data may need review.
A match needs context.Decide who you want to understand
Explore the profile and group guests with criteria that matter to your team. Choose signals you can explain, instead of collecting data without a purpose.
A segment answers a question.Prepare the next interaction
Bring context into reception or marketing work. Before a campaign, check that the channel and permissions allow that communication.
Having an email is not the same as having permission.
Before you connect.
What data can I connect?
It depends on your systems and the connections available. We start with your sources, their fields and how your team wants to use them to define a specific scope.
Will every record identify the same guest?
There is no guaranteed match for every record. Identification depends on the data available and its quality. Ambiguous cases need review and a defined approach.
Does a profile allow me to send campaigns?
Having a profile does not imply permission to send marketing communications. Channels, preferences and consent need to be reviewed separately before a campaign is activated.
How do we start with my hotel?
We review a specific journey, the systems involved and the data needed with your team. We then define the connections, scope and setup conditions.
Your data already tells a story. Let’s connect it.
Tell us which systems you use and what your team needs to know about its guests. Let’s define the first journey together.
Request a CDP demoExplore the connections