Insights

What Is a Guest 360 Profile—and What Data Should It Contain?

Learn what a Guest 360 profile is, which vacation rental data belongs in it, and how unified guest context improves service, marketing, and repeat bookings.

Petar Ojdrovic

Yada

·

4 min read

A Guest 360 profile is a unified view of the relationship between one guest and your vacation rental brand.

It should answer three questions quickly:

  1. Who is this guest?

  2. What has happened across our relationship?

  3. What should the team or system know before taking the next action?

That sounds simple. In practice, the information is often scattered across reservations, inboxes, campaign tools, loyalty systems, guidebooks, and spreadsheets.

Guest 360 brings the useful pieces together.

Guest 360 is not a giant data dump

The goal is not to display every event the business has ever collected.

The goal is to show the context required for better decisions.

A reservation agent needs to see different details than a database engineer. A marketing manager should not need to open six tabs to understand whether a guest is a high-value repeat visitor.

A strong profile is complete enough to be useful and structured enough to be understood.

1. Guest identity

The profile should begin with stable identity information:

  • Name

  • Known email addresses

  • Known phone numbers

  • Preferred contact details

  • Brand or portfolio relationship

  • Household or linked-guest information when appropriate

  • Source records used to build the profile

Identity resolution should be cautious.

Two people sharing a surname or phone number should not be merged automatically without enough supporting evidence. The system needs confidence and a way to undo incorrect matches.

2. Reachability and consent

Contact information is not the same as permission to market.

The profile should show:

  • Email eligibility

  • SMS eligibility

  • Opt-in source

  • Opt-out or suppression status

  • Invalid or unreachable channels

  • Communication preferences

  • Recent contact history

This needs to be current and shared across campaigns, journeys, and AI agents.

3. Reservation history

The guest timeline should include:

  • Confirmed stays

  • Cancelled stays

  • Properties visited

  • Check-in and checkout dates

  • Booking channel

  • Direct versus OTA booking

  • Stay value

  • Party size when available

  • Lead time

  • Length of stay

The profile should make patterns visible without requiring manual calculation.

4. Lifetime value

Guest lifetime value can be more useful than the value of the current reservation.

The profile may include:

  • Total booked revenue

  • Direct-booked revenue

  • Number of stays

  • Average booking value

  • Average length of stay

  • Ancillary purchases

  • Refunds or credits where relevant

Lifetime value should be defined clearly. Teams need to know whether it includes cancelled bookings, taxes, fees, and attributed revenue.

5. Property and destination preferences

Preferences can be observed or explicitly provided.

Examples:

  • Markets visited

  • Property type

  • Bedroom count

  • Pet-friendly requirements

  • Pool or hot-tub interest

  • Accessibility needs

  • Preferred season

  • Typical party size

  • Drive-to versus fly-to behavior

Preferences should help the business become more relevant, not creepy.

Use information the guest provided or behavior reasonably implies. Avoid pretending the system knows more than it does.

6. Conversation history

Important guest context often lives in messages:

  • Questions asked before booking

  • Common concerns

  • Booking objections

  • Service issues

  • Promises or exceptions

  • Campaign replies

  • Human handoffs

The profile does not need to expose every raw message by default. A useful summary and access to the original thread can be enough.

7. Campaign and journey engagement

Marketing context can include:

  • Campaigns received

  • Sends, opens, clicks, and replies

  • Links visited

  • Journeys entered

  • Journey state

  • Recent offers

  • Suppression or cooldown

  • Bookings attributed to engagement

This prevents the business from treating a guest as unaware of an offer they already discussed.

8. Loyalty and referral status

If the operator runs a loyalty program, the profile should include:

  • Membership status

  • Tier

  • Points balance

  • Earning activity

  • Redemptions

  • Reward eligibility

  • Referral activity

  • Milestones approaching

Loyalty should be part of the relationship, not a separate identity.

9. Open opportunities

A Guest 360 profile should show active commercial work:

  • Current inquiry

  • Property and requested dates

  • Opportunity stage

  • Estimated value

  • Last guest response

  • Current owner

  • Next recommended action

  • Agent or journey status

This tells the team whether the guest is already in a live booking conversation.

10. Predictive and derived signals

The profile can also include calculated signals:

  • Predicted trip window

  • Likelihood to book again

  • Booking intent

  • Churn or inactivity risk

  • Preferred channel

  • Guest segment

  • Confidence behind the prediction

Derived data should be labeled. A prediction is not a fact.

What should not appear in the profile?

Do not collect information simply because it might be possible.

Avoid:

  • Unnecessary sensitive personal information

  • Unsupported assumptions

  • Private message content unrelated to the business purpose

  • Unverifiable labels about personality or behavior

  • Data the team cannot protect or justify using

Good guest intelligence is purposeful and bounded.

How different teams use Guest 360

Reservations

  • Recognize repeat guests

  • Understand the current opportunity

  • Recommend a relevant property

  • Continue a conversation without asking the guest to repeat everything

Marketing

  • Build precise audiences

  • Exclude guests already in an active opportunity

  • Personalize based on real history

  • Measure repeat and direct booking behavior

Guest experience

  • See important preferences

  • Recognize previous issues

  • Deliver consistent service

  • Avoid conflicting promises

AI agents

  • Assemble trusted context

  • Decide within guardrails

  • Draft relevant actions

  • Escalate with a complete brief

How to measure profile quality

A Guest 360 system should improve:

  • Duplicate-record rate

  • Repeat-guest recognition

  • Time required to understand a guest

  • Marketable guest coverage

  • Segmentation accuracy

  • Opportunity response time

  • Direct-booking attribution

  • Cross-team consistency

If the profile contains more data but does not improve decisions, it is not doing its job.

The real value of Guest 360

Guests experience one brand.

They do not experience your PMS, campaign tool, loyalty system, inbox, and guidebook as separate products.

Guest 360 gives the business the same unified perspective the guest assumes it already has.

That perspective powers better service, more relevant marketing, and a stronger path from one stay to the next.

Learn how Yada creates a living guest record with vacation rental CRM.

See your next direct-booking opportunity

In a 20-minute demo, we’ll map the campaigns and guest segments that can help your portfolio bring past guests back.

See your next direct-booking opportunity

In a 20-minute demo, we’ll map the campaigns and guest segments that can help your portfolio bring past guests back.

See your next direct-booking opportunity

In a 20-minute demo, we’ll map the campaigns and guest segments that can help your portfolio bring past guests back.