Insights
How guest data actually works inside a hotel group.
Long-form guides on identity resolution, guest data, and the one record every agent has to read. Written for the IT, operations and commercial leaders who have to make it work.
Guest data · September 2026
Why hotel loyalty programmes miss repeat guests
Loyalty programmes fail at recognition, not rewards. Enrolment is a separate event from staying, and the stay is stored as unlinked copies.
Guest data · August 2026
What a hotel master profile is (and why the PMS one is not it)
A guest can book a room, eat at the restaurant and visit the spa yet appear as three different people across hotel systems. A hotel master profile brings those fragments together as one durable guest record.
Guest data · August 2026
What a hotel semantic layer is, and what it is not
A hotel semantic layer gives guests, reservations, stays and folios consistent meanings across systems and agents. It does not determine which records belong to the same person. That is guest identity resolution.
Guest data · August 2026
Guest identity resolution for hotel groups: merging fragmented profiles across PMS, POS and booking engine
The same guest can exist as several unconnected records across a group's properties and systems. This guide explains why it happens, what identity resolution actually does, and why the resolved record is the layer your agents run on.
Guest data · August 2026
Hotel CDP vs guest identity layer: what the two terms actually mean
A CDP and an identity layer look the same on a slide. They differ in what they are for, who ends up controlling the record, and what survives when you change vendors. We build one of them, so the case for the other is put carefully.