These filters segment by who the guest is rather than what they booked: their history with you, what is on their profile, and what they have done in your forms and lists. Sixteen of them, grouped below by the question they answer.
Every filter has an Exclude selected option that inverts it, and filters combine with AND. See Audiences.
Their history with you
Count of previous reservations. How many past stays. Set it to 0 for first-time guests, or 5 and above for regulars. The settings are worth knowing:
Property selector. Count stays at specific properties only. Leave it empty and every property you can see is counted, which is the default. Chosen properties appear on the filter's summary card.
All time toggle. On, it looks at the guest's whole history. Off, it opens a time window.
Guest type. Narrow to a type such as leisure or corporate.
Count of future reservations. The same, forward-looking, with Within the next X days instead. Set it to 0 to find guests with nothing booked, which is the re-engagement audience.
Total spend. What a guest has spent with you across their whole history. Four things about it matter:
Every role counts. Reservations the guest booked for other people are included, so the person who actually paid is in the audience rather than skipped.
Each reservation counts once per guest, even where they hold more than one role on it.
Totals are not additive across guests. A booking counts towards the total of everyone linked to it, so you cannot add two guests' figures together and reconcile them against revenue.
Cancelled reservations are excluded, and amounts are in your organisation's base currency.
This is the same figure as the Total money spent column on the audience table. It is not Reservation balance, which is money outstanding on one booking and sits in Audience filters: reservation.
Guest is in hotel. Guests currently checked in, within a time range you set. This is the in-stay filter: room service, late checkout, the bar.
Who they are
Birthday. Filters on the birthday date. Excluding is as useful as including, to keep birthday guests out of a general campaign when they are already getting a dedicated one.
Guest generations. Birth year grouped into named bands: Silent Generation (1928 to 1945), Baby Boomer (1946 to 1964), Gen X (1965 to 1979), Millennial (1980 to 1995), Gen Z (1996 to 2011), Gen A (2012 to 2024). Useful when you have birth years but do not want to work with exact dates.
Guest gender. Male, Female, Other, or Unknown where it was never captured.
Guest location. Country, region, or city of origin. The filter for a campaign written in one language, or an offer that only makes sense to guests within driving distance.
Guest has company. Whether the profile is linked to a company. The quickest split between business and leisure.
What is on the profile
Guest profile info. Guests who have a given field filled in: first name, last name, birthdate, nationality, identity document type, identity document number.
Missing profile info. The same list, inverted: guests who are missing it. Both filters have Exclude selected as well, so either one can be flipped to do the other's job.
The practical use is data quality. Filter for guests missing a birthdate and you have the list to chase before running a birthday campaign that would otherwise skip them silently.
Email usernames. Matches the part of the address before the @. Type one or more prefixes and select + to add them. For matching on the domain instead, use Receiver email domains in Audience filters: reachability.
Forms, lists, and tasks
Guest has submitted form. Whether this guest completed a chosen form. Turn Exclude selected on and you have everyone who has not, which is the reminder audience.
Form field value. Goes a level deeper: not whether they answered, but what they answered. A guest who picked "anniversary" in a pre-stay form is a different audience from one who picked "business trip". See Segment guests by a form field value.
Guest list. Membership of a list you built by hand. Include it to target that list, exclude it to suppress them. See The Guests List.
Guest has task with title. Guests with a task assigned under a specific title, for targeting people at a known point in a workflow.
What this does not do
Profile data comes from your PMS. Gender, nationality, and birthdate are only as complete as what your PMS sends, so a filter on any of them silently drops every guest whose record is blank.
Total spend cannot be reconciled against revenue. The same booking counts for every guest linked to it, by design.
These filters do not check reachability or consent. Add Reachable first.
Guest list membership is manual. Lists do not update themselves as guests come and go, so an old list quietly goes stale.
What to do next
To add booking conditions on top, see Audience filters: reservation.
Getting help
Open Help at the bottom of the left menu and choose Talk to Us, or email support@bookboost.io.