Field Mapping Spectra

Here you can get an overview of the fields available in the Spectra integration.

Guest Field Mapping

Fields configured as part of the integration are created. They can be edited for each individual customer under the guest’s contact card in Heyloyalty. The five spectra* fields are automatically created in the list. By default, contacts are matched via email or cell phone number; a guest with no value in the match field is skipped.

Fields on the Heyloyalty list	From Spectra	Note
email	email	Default field for match contact
mobile	Phone	Standard field – Reduced to numbers only.
firstname	firstname	Default Field
lastname	Last Name	Default Field
address	address1	Default field – First address line only.
ZIP Code*	zip_code	Customer Field
city	city	Default Field
Country	CountryCode	Default field—country code, not a country name.
Spectra Guest ID*	ID	Customer Field – The guest’s ID in Spectra. Locked—it cannot be overwritten.
spectra_language*	LanguageCulture	Customer Field – Useful for campaigns organized by language.
Spectra segments*	derived	Customer field – comma-separated. Used for Spectra segments
Spectra Newsletter*	derived	Customer Field – Newsletter Permission

Reservation Mapping

The fields are created via the list’s tracking integration, and they are the ones that segmentation, automations, and merge fields read, among other things. They are all pre-filled during mapping in the Spectra integration; a field mapping that is left blank is simply not sent to Heyloyalty. If a reservation is recorded without an email address or phone number, the reservation is skipped entirely.

Tracking Field	From Spectra	Contents
Identifiers
booking_id	ReservationGuid	The reservation’s unique ID. Creates or updates a reservation.
product_id	ReservationGuid
reservation_id	ReservationId	The reservation number that hotel staff see in Spectra.
order_number	Reservation ID
Dates and Length of Stay
booking_date	Created	When the reservation was made.
arrival_date	Arrival	Check-in.
departure_date	Arrival	Also check-in. The day the guest arrives.
return_date	Departure	Check-out. “Return date” is the day the guest leaves.
night_count	derived	Number of full nights between check-in and check-out.
lead_time_days	derived	Number of days from booking to arrival. Useful for scheduling mailings before arrival.
Hotel and Room
hotel_code	HotelCode	The chain’s short code for the hotel or branch.
hotel_name	Look up	Retrieved from Spectra’s hotel list. If the name is not found, the code is used.
destination	look up	The city where the hotel is located. Empty if the API user does not have access to the hotel list.
room_type	Room.RoomType
room_number	Room.RoomNumber
Commercial
price	derived	The sum of the packages included in the reservation and any add-on packages.
rate_plan	PriceCodes.PriceCode
market_group	Markets.MarketDesc	Spectra’s market segmentation, e.g., leisure vs. business.
source	Sources.SourceDesc	Business source.
booking_channel	Channel	Where the booking came from.
reservation_type	ReservationType	Restaurant and spa reservations are included.
part_of_conference	PartOfGroupOrConference	Yes/No. The only way to distinguish between conference and group transactions.
Guest on the reservation
guest_name	derived	The name of the reservation, or the first and last name from the guest profile.
adult_count	NumberOfAdults
child_count	NumberOfChildren	Distinguishes between families and couples.
membership_number	Guest.MembershipNumber	Loyalty membership, if the hotel has one.
vip_status	Guest.Vip
Status
status	Derived	Sent as a purchase or as a cancellation.

---