Glossary of Filter Terms and Date Presets

Mariia Korostashevych

Updated August 12, 2026 18:18

Purpose	Understand what each filter operator and date preset means in Reporting and Cloudbeds Insights, and when to use each one.
Best for	Property owners, managers, front desk and finance teams, admins, and Cloudbeds Insights Authors who view, filter, build, or troubleshoot reports.
Use this when	You need to choose a filter, confirm what a filter returns, compare similar date presets, or understand why report results change after a filter is applied.
Requirements	The permissions and product capabilities needed for the report action you want to perform. See Access and dependencies.
Expected result	You can correctly interpret and apply filter operators and date presets, and recognize when a filter choice is affecting your report results.

Introduction

Reports in Cloudbeds use filters to narrow results down to the records you need, whether you are opening a Cloudbeds Report or building a custom one in Cloudbeds Insights. Each filter is made up of an operator, such as equal to or contains, and for date fields, a set of presets like Last 7 Days or Current Month.

This glossary explains what each filter operator and date preset returns, so you can use filters correctly and understand why a report displays certain results. Users with Reporting access and the appropriate Viewer permission can apply these filters to Cloudbeds Reports. Creating and permanently saving new filtered reports from scratch requires Cloudbeds Insights, Builder capabilities, and the appropriate Author permission.

Who this affects and how
Access and dependencies
Filter operators
Date filters

Who this affects and how

The same filter definitions apply across Reporting and Cloudbeds Insights, but how you use them depends on the reporting work you are responsible for and the permissions available to you.

Role	What to know
Front desk and operational users	Use filter operators and date presets to narrow reports for day-to-day questions such as arrivals, departures, reservation details, or recent activity. Confirm the definition of a filter when the results do not match the period or records you expected.
Managers and finance teams	Pay particular attention to date presets when comparing operational or financial periods. Calendar-based and rolling presets can return different date ranges even when their names appear similar.
Property owners	Use the date filter definitions to distinguish full-period, period-to-date, historical, and forward-looking views before interpreting report totals or comparing performance.
Admins and Cloudbeds Insights Authors	Review Access and dependencies before creating or permanently saving filtered reports. Viewer and Author permissions determine whether you can only view and temporarily filter a report or also use Builder capabilities to create and save reporting content.

Access and dependencies

Confirm the following before applying or building filters:

Reporting access to view Cloudbeds Reports.
Viewer permission for the specific dataset or report you want to view. Viewer access is granted per dataset, so having it for one report does not automatically grant access to every report. See Role privileges for how dataset-level access works.
Cloudbeds Insights and Author permission for the same dataset, if you are creating a report from scratch or permanently saving changes such as Save As, using the report-building capabilities (Builder) available to Cloudbeds Insights users with Author permission.
The field type you are filtering on. The operators and date presets available to you depend on whether the selected field is text, number, or date.

With these confirmed, you're ready to work through the glossary itself. It starts with Filter operators, the general rules that apply no matter the field type, before narrowing into Date filters for the presets that only become available once you're working with a date field.

Filter operators

Filter operators are the general comparison and matching rules you'll see throughout Cloudbeds Reports and Builder. They work the same way regardless of field type, so an operator like equal to or contains behaves consistently whether you're filtering a name, a number, or a date.

A few operators do more when the selected field is a date. For example, greater than or equal to unlocks a dedicated set of date presets covered in Date filters. Because of this, a term like All or Is Not Null may show up again in that section with a more specific, date-driven meaning: the table below explains the general behavior first, and the date-specific version follows in its own section.

Filter term	Definition	When to use it
All	Shows all records for the selected field, including values that are null (missing) or empty.	Use when you want the filter present without excluding any results, such as while building a report before narrowing it down.
Null	Checks if the field contains no value at all. Filters out records that have data present.	Use to find incomplete records, such as reservations missing a required field, so you can follow up.
Is Not Null	Shows only records where the selected field contains a value; records with no value are excluded.	Use when you only want complete records, such as reservations with a confirmed check-in date. To include null or empty values too, use All instead.
equal to	Checks if a value matches exactly. Example: reservation number equal to 1162241480445 returns only that reservation.	Best for looking up one specific, known record.
is not equal to	Checks if a value does not match. Example: reservation number is not equal to 1162241480445 excludes only that reservation.	Use to exclude one known record while keeping everything else.
greater than or equal to	Returns records at or after the value. Example: Check-In Date greater than or equal to 2024-11-05 returns that date and every date after. For a date field, this operator surfaces the presets in Date filters.	Use for open-ended, forward-looking questions, such as everything from this date forward.
greater than	Returns records strictly after the value. Example: Check-In Date greater than 2024-11-05 returns 2024-11-06 onward.	Use instead of greater than or equal to when the boundary date itself should be excluded.
less than	Returns records strictly before the value. Example: Check-In Date less than 2024-11-05 returns 2024-11-04 and earlier.	Use for reviewing history up to, but not including, a cutoff date.
less than or equal to	Returns records at or before the value. Example: Check-In Date less than or equal to 2024-11-05 returns that date and earlier.	Use for backward-looking questions such as everything through this date, including the date itself.
in	Checks if a value is part of a defined list. Example: Transaction Status in (Pending, Posted) returns both statuses. Displayed as a checkbox list.	Useful for reconciliation, when you need to isolate a specific combination of statuses at once.
is not in	Excludes a defined list of values. Example: Transaction Status is not in (Pending) returns everything except pending. Displayed as a checkbox list.	Useful for excluding known statuses you don't want cluttering a reconciliation report.
contains	Matches text anywhere in the field, not case sensitive. Example: guest first name containing "ro" matches Rosie, Ronald, and Deborah-Rose.	Useful for a partial or uncertain search when you don't know the exact spelling or position of the text.
does not contain	Excludes records containing that text, not case sensitive. Example: first name does not contain "ver" excludes Veronica, Oliver, and Iver.	Use to exclude records containing a known snippet of text, without needing to know its position.
begins with	Matches text at the start of the field, not case sensitive. Example: begins with "Jo" matches John, Joanna, and Johnson, but not Jeremy or Juan.	Useful when you know how a value starts, such as a source code or ID prefix.
does not begin with	Excludes records starting with that text, not case sensitive.	Use to exclude a known prefix, such as filtering out records from a specific source.
ends with	Matches text at the end of the field, not case sensitive. Example: ends with "th" matches Elizabeth, not Luz.	Useful when you know how a value ends, such as a document or file suffix.
does not end with	Excludes records ending with that text, not case sensitive.	Use to exclude records with a known suffix.
is empty	Checks if the field is empty or contains no usable data.	Useful for a lighter-weight check than Null when you just need to spot blank entries in a text field.
is not empty	Checks if the field contains a value, including a non-visible space.	Use to confirm a text field has content, including cases where only a hidden space was entered.

Date filters

Date filters are the presets and behaviors available specifically when the selected field is a date, such as Last 7 Days or Current Month.

This section is organized by date option rather than by operator. Because of that, a label already covered in Filter operators, such as All or Is Not Null, may reappear here with a meaning that's specific to date fields rather than a general one.

Every date filter behaves in one of two ways, Fixed or Rolling. Knowing which type you are using explains why a report's totals shift, or don't, from one day to the next.

Type	Behavior	When to use it	Example
Fixed	Always resolves to the same date range, regardless of when you run the report.	Use when you need consistent, repeatable results, such as month-end reporting or comparing the same period across different report runs.	Last Month is the full previous calendar month, every time.
Rolling	Recalculates daily, relative to today.	Use when you want a report that automatically stays current without editing it each day, such as a dashboard you check regularly.	Last 7 Days always includes today and the 6 days before it. The window moves every day.

Day

Filter	Returns	Type	When to use it
Today	Today's date only.	Rolling	Useful for daily operational checks, such as today's arrivals or departures.
Yesterday	The previous calendar day.	Rolling	Useful for end-of-day reconciliation done the next morning.
Tomorrow	The next calendar day.	Rolling	Useful for next-day arrival or housekeeping planning.

Week

Filter	Returns	Type	When to use it
Current Week	The full current calendar week, including any remaining future days.	Fixed	Useful for weekly planning that needs to account for what's still ahead.
Last Week	The full previous calendar week.	Fixed	Useful for week-over-week comparisons of completed activity.
Next Week	The full next calendar week.	Fixed	Useful for forward staffing or arrivals planning.
Last 7 Days	Today plus the 6 days before it.	Rolling	Useful for a rolling, always-current snapshot rather than a fixed calendar week. Because it rolls, totals shift daily.
Next 7 Days	Today plus the 6 days after it.	Rolling	Useful for a rolling short-term forecast, such as upcoming arrivals regardless of the day of the week.

Month

Filter	Returns	Type	When to use it
Current Month	The full current calendar month (1st to last day), including future dates.	Fixed	Use for planning or forecasting, such as occupancy planning. Because future dates are included, totals may differ from reports measuring only completed activity.
Current Month MTD	1st of the current month through today.	Rolling	Use for in-progress performance tracking, such as revenue booked so far this month. Will not match Current Month until the month has fully ended.
Last Month	The full previous calendar month.	Fixed	Useful for closed-period reporting and month-over-month comparisons.
Next Month	The full next calendar month.	Fixed	Useful for forward planning, such as reviewing confirmed bookings for the month ahead.
Last 30 Days	Today plus the 29 days before it.	Rolling	Useful for a rolling trailing-month view. Will not line up with Last Month, so avoid mixing the two in the same comparison.
Next 30 Days	Today plus the 29 days after it.	Rolling	Useful for a rolling short-term forecast not tied to calendar month boundaries.

Quarter

Filter	Returns	Type	When to use it
Current Quarter	The full current calendar quarter (Q1 January to March, Q2 April to June, Q3 July to September, Q4 October to December), including future dates.	Fixed	Use for full-quarter planning. Because future dates are included, totals may overstate quarter-to-date performance.
Current Quarter QTD	1st day of the current quarter through today.	Rolling	Use for live, in-progress quarter tracking, such as revenue pace against a quarterly target.
Last Quarter	The full previous calendar quarter.	Fixed	Useful for closed-quarter reporting and quarter-over-quarter comparisons.
Next Quarter	The full next calendar quarter.	Fixed	Useful for forward budgeting and planning cycles.

Year

Filter	Returns	Type	When to use it
Current Year	The full current calendar year (January 1 to December 31), including future dates.	Fixed	Use for annual planning; totals include bookings not yet realized.
Current Year YTD	January 1 of the current year through today.	Rolling	Use for year-to-date performance tracking and budget-versus-actual reviews.
Last Year	The full previous calendar year.	Fixed	Useful for year-over-year comparisons of fully completed activity.
Next Year	The full next calendar year.	Fixed	Useful for long-range forecasting and budget preparation.

Custom

Filter	Returns	Type	When to use it
All	Any date. No date filter applied.	Fixed	Useful as a starting point before narrowing down to a specific period.
Custom Date	A single date you choose.	Fixed	Best for investigating or reconciling one exact day.
Custom Date Range	A range you set, using fixed dates or relative dates.	Fixed or Rolling	Use when no named preset matches the exact period you need. See Choosing between Custom Date and Custom Date Range.

Custom Date Range has four modes:

Mode	What it returns	When to use it	Example
Custom dates	A specific start and end date. Both dates are included in results.	Use for a fixed, one-time reporting window, such as a specific promotion period.	5/10/2025 to 5/19/2025 includes 5/10, 5/19, and every day between.
Date to end of data	A start date with no end boundary. All records from that date forward through the latest available data.	Use to capture everything since a known milestone, such as a system change.	1/1/2024 onward, for everything since.
Beginning of data to date	An end date with no start boundary. All records from the earliest available data up to and including that date.	Use for full historical pulls up to a known cutoff.	Through 12/31/2023, for historical pulls.
Custom relative dates	A rolling range you define by choosing a number, a unit of time, and a direction. Units can be days, weeks, months, or years, and the direction can be prior or later. The range updates automatically each day.	Use when you need a rolling period that no named preset covers and want the report to stay current without changing the dates manually.	30 days prior, 2 weeks later, or 3 months prior.

Null checks (date fields)

Filter	What it returns	Type	When to use it
Is Null	Has no date value.	Fixed	Useful for finding records missing an expected date, such as a reservation with no checkout recorded.
Is Not Null	Has a date value.	Fixed	Useful for limiting a report to only complete, dated records.

Choosing between Custom Date and Custom Date Range

Use this section when none of the named presets in Day, Week, Month, Quarter, or Year fit what you need, and you have to decide between filtering on one exact date or filtering on a period, an open-ended range, or a rolling window. Start by asking what kind of question you are answering:

Use Custom Date when your question points to a single specific date, such as checking what happened on one particular check-in date.

Use Custom Date Range when your question points to a period of time rather than one date. Custom Date Range covers four different modes, depending on whether that period has a fixed start and end, is open-ended on one side, or should roll forward automatically:

Custom dates for a fixed range with a specific start and end. Both boundary dates are included.
Custom relative dates for a rolling range no preset covers, such as "45 days prior" or "2 weeks later." It updates automatically each day, so saved views stay current without manual changes.

See Custom for the full definitions of all four modes, including the two open-ended modes (date to end of data, and beginning of data to date).

Any Reporting user can apply a custom relative date range temporarily while viewing a Cloudbeds Report. Saving it as part of a new or edited report requires Cloudbeds Insights and the appropriate Author permission to use its report-building capabilities.

Commonly confused pairs

These preset pairs look similar but return different results. Checking the difference here can save troubleshooting time later.

Pair	The difference	Example
Current Week vs. Last 7 Days	Current Week uses your configured calendar week (fixed boundaries). Last 7 Days is a rolling 7 day window ending today, so it always crosses week boundaries.	A front desk agent pulling arrivals for "this week" wants Current Week. If they pick Last 7 Days instead on a Wednesday, the report spans into last week and misses part of the current one.
Current Month vs. Current Month MTD	Current Month is the entire month, including future dates. MTD stops at today, so use it for in-progress reporting.	A manager checking performance so far this month wants Current Month MTD. Current Month would also include future reservations and make revenue look higher than what has actually happened.
Current Quarter vs. Current Quarter QTD	Current Quarter is the full quarter (past and future dates). QTD runs from quarter start through today, so use it for live performance tracking.	A GM tracking quarter-to-date occupancy wants QTD. Current Quarter would pull in bookings for future dates in the quarter and overstate how the quarter is actually trending.
Last 30 Days vs. Last Month	Last Month is a clean calendar month, for example April 1 to 30. Last 30 Days rolls from today, so totals shift daily.	A finance team comparing full calendar months month over month wants Last Month. Last 30 Days would shift a day earlier every time the report runs, making the periods uneven to compare.

You should now be able to interpret and choose the right filter for your reporting question. For broader context on how Reporting and Cloudbeds Insights relate, and how report access is controlled, review these additional resources: