Loading

Marketing Cloud Engagement | How Monthly Operators Work for Date Fields (Data Filter and Journey Builder)

게시 일자: Jul 15, 2026
상세 설명

When you specify a monthly operator (such as "today + 1 month" or "today - 1 month") on a date field in Data Filter or Journey Builder, if the calculated date does not exist in the target month, the system automatically selects the last day of that month. This article covers the behavior for common patterns and explains calculations involving February 29 in leap years.

솔루션
The behavior described in this article applies to the following features:

  • Journey Builder Decision Split Activity branch conditions
  • Journey Builder Exit Criteria
  • Data Filter conditions

1. Base Behavior (Date Arithmetic)

When performing monthly arithmetic (such as "+1 month" or "-1 month"), the system automatically determines the target date using the following priority order:
  • If the same day exists: The same date in the next or previous month is selected as-is.
  • If the same day does not exist (end-of-month fallback): If that date does not exist in the target month, the last day of that month is automatically selected.

2. Frequently Asked Questions (FAQ)

Q. If today is 7/31 and "today - 1 month" is specified, which records are targeted?
A. 6/30 is targeted. Since June does not have a 31st day, the base rule (end-of-month fallback) applies and 6/30, the last day of June, is automatically selected.

Q. If today is 1/31 and "today + 1 month" is specified, which records are targeted?
A. 2/28 is targeted (2/29 in a leap year). Since February does not have a 31st day, 2/28, the last day of February, is automatically selected. In a leap year, 2/29 becomes the last day and is selected instead.

Q. What happens when a date other than end-of-month (for example, 1/15 or 1/30) is used with "today + 1 month"?
A. The behavior depends on whether the specified date exists in the calculated target month.

  • For 1/15 (target: 2/15): Since the 15th exists in February, 2/15 is selected as-is.
  • For 1/30 (target: 2/28 or 2/29): While 1/30 is not an end-of-month date, February does not have a 30th day, so the base rule applies and the last day of February (2/28 or 2/29) is automatically selected.

3. Appendix

Q. Does the behavior above also apply to Journey Builder Decision Split Activity conditions and Exit Criteria?
A. Yes, the behavior is identical. The same date arithmetic logic is used. When a date field with a monthly operator is used in a Decision Split Activity condition or Exit Criteria, all of the rules above apply.

Q. What should I do if I do not want the result to fall on the last day of the month when using "today - 1 month" (for example, I only want to target data from the 31st of each month)?
A. The monthly operator alone cannot strictly filter for the 31st. Because the monthly operator returns "the same day in the next or previous month (or the last day if that day does not exist)," the last day of the month is selected in months where the 31st does not exist. If you need to target a specific date precisely, consider combining the "today + N days" operator or adding the target date as a separate fixed condition.
Knowledge 기사 번호

005387396

 
로드 중
Salesforce Help | Article